| 3 | Approval of the Agenda | |
|---|---|---|
| R3-210001 | RAN3#111-e Meeting Agenda | Chairman |
| 4 | Approval of the minutes from previous meetings | |
| R3-210002 | RAN3#110-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-210531 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-210532 | List of E-mail Discussions | RAN3 Chairman |
| 7 | General, protocol principles and issues | |
| R3-210629 | Discussions on Chapter 10 in S1AP and NGAP | Ericsson |
| R3-210630 | Correction for Chapter 10 | Ericsson |
| R3-210631 | Correction for Chapter 10 | Ericsson |
| R3-211049 | CB: # 81_Ch10_NGAP_S1AP - Summary of email discussion | Ericsson - moderator |
| R3-211086 | Correction for Chapter 10 | Ericsson |
| R3-211087 | Correction for Chapter 10 | Ericsson |
| R3-211120 | Correction of NRPPa section 10 | Ericsson, Qualcomm Incorporated, Intel, Nokia, Nokia Shanghai Bell, Huawei |
| 8.1 | New Incoming LSs | |
| R3-210021 | LS response to TCCA on Public Safety | GSMA 5G Joint-Activity (5GJA) |
| R3-210022 | LS on mandatory support of full rate user plane integrity protection for 5G | CT WG1 |
| R3-210023 | LS on Cell Configuration within TA/RA to Support Allowed NSSAI | CT WG1 |
| R3-210024 | Withdrawal of IEEE Std 802.1D-2004 | IEEE 802.1 |
| R3-210025 | LS on Latency of NR Positioning Protocols | RAN WG1 |
| R3-210026 | LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G | RAN WG2 |
| R3-210027 | Reply LS on early UE capability retrieval for eMTC | RAN WG2 |
| R3-210029 | LS to RAN3 on small data transmission | RAN WG2 |
| R3-210030 | Reply LS on the user consent for trace reporting | RAN WG2 |
| R3-210031 | Reply LS on LS on restricting the rate per UE per network slice | RAN WG2 |
| R3-210034 | Reply LS on System support for Multi-USIM devices | RAN WG2 |
| R3-210035 | LS on DL RRC segmentation | RAN WG2 |
| R3-210037 | AN-PDB and PER targets for satellite access | SA WG2 |
| R3-210038 | LS on Aerial Features for Unmanned Aerial Vehicles | SA WG2 |
| R3-210040 | Reply LS on early UE capability retrieval for eMTC | SA WG2 |
| R3-210043 | Reply LS on MDT Stage 2 and Stage 3 alignment | SA WG5 |
| R3-210056 | Feedback on data forwarding and context fetch for SDT | Nokia, Nokia Shanghai Bell |
| R3-210057 | Reply LS on RAN2 agreements on small data transmission | Nokia, Nokia Shanghai Bell |
| R3-210089 | Network support for the RRC segmentation | Nokia, Nokia Shanghai Bell |
| R3-210090 | LS on RRC segmentation | Nokia, Nokia Shanghai Bell |
| R3-210091 | LS on RRC segmentation | Nokia, Nokia Shanghai Bell |
| R3-210092 | [draft] Response LS on DL RRC segmentation | Nokia, Nokia Shanghai Bell |
| R3-210139 | Support of RACH based small data transmission | Huawei |
| R3-210140 | Support of CG based small data transmission | Huawei |
| R3-210141 | [Draft] Reply LS on small data transmission | Huawei |
| R3-210187 | Discussion on SDT with/without UE context relocation | ZTE |
| R3-210188 | CR 38.300 for support of small data transmission | ZTE |
| R3-210189 | CR 38.423 for support of small data transmission | ZTE |
| R3-210190 | [DRAFT] Reply LS on small data transmission | ZTE |
| R3-210193 | Discussion on DL RRC segmentation | ZTE |
| R3-210194 | [DRAFT] Reply LS to DL RRC segmentation | ZTE |
| R3-210208 | Discussion on RRC Segmentation | Samsung |
| R3-210209 | CR on RRC segmentation over X2 | Samsung |
| R3-210210 | CR on RRC segmentation over Xn | Samsung |
| R3-210211 | CR on RRC segmentation over F1 | Samsung |
| R3-210243 | SDT support with and without UE context relocation | NEC |
| R3-210244 | TP for SDT BL CR for TS 38.423 (SDT support with and without UE context relocation) | NEC |
| R3-210245 | Indication of node capability to support DL RRC segmentation | NEC |
| R3-210322 | Synching the Collection Period values to those specified in TS32.422 | Ericsson |
| R3-210323 | Synching the Collection Period values to those specified in TS32.422 | Ericsson |
| R3-210332 | On RAN3 impacts of NR small data transmission | Qualcomm Incorporated |
| R3-210333 | [Draft] Reply LS to RAN3 on small data transmission | Qualcomm Incorporated |
| R3-210424 | Discussion on synching the collection period values to SA5 specifications | Ericsson |
| R3-210425 | [draft] Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-210499 | NR Small Data Transmission in INACTIVE | Ericsson |
| R3-210500 | [DRAFT] Reply LS to RAN3 on small data transmission | Ericsson |
| R3-210649 | On DL RRC segmentation | Ericsson |
| R3-210650 | [DRAFT] Reply LS on DL RRC segmentation | Ericsson |
| R3-210753 | On RAN2 LS on small data transmission | Intel Corporation |
| R3-210754 | [DRAFT] Reply LS on small data transmission | Intel Corporation |
| R3-210788 | DL RRC segmentation | Huawei |
| R3-210789 | DL RRC segmentation | Huawei |
| R3-210790 | DL RRC segmentation | Huawei |
| R3-210791 | DL RRC segmentation | Huawei |
| R3-210792 | DL RRC segmentation | Huawei |
| R3-210793 | [Draft] Reply LS on DL RRC segmentation | Huawei |
| R3-210832 | Discussion on small data transmission for Inactive | Samsung |
| R3-210844 | [DRAFT] Reply LS on small data transmission | Samsung |
| R3-210880 | Consideration on small data transmission with and without anchor relocation | LG Electronics |
| R3-210925 | Discussion on small data transmission with and without anchor relocation | CMCC |
| R3-210926 | [Draft]Reply LS on small data transmision | CMCC |
| R3-210946 | Support of Unmanned Aerial Vehicles | Ericsson |
| R3-210947 | [DRAFT] Reply LS on Aerial Features for Unmanned Aerial Vehicles | Ericsson |
| R3-210948 | Introduction of Unmanned Aerial Vehicle UE authorization information | Ericsson |
| R3-210949 | Introduction of Unmanned Aerial Vehicle UE authorization information | Ericsson |
| R3-210953 | LS/o on Establishment of new Focus Group on Autonomous Networks | ITU-T Study Group13 |
| R3-211007 | Response to R3-210946 | HUAWEI Technologies Japan K.K. |
| R3-211035 | LS on port allocation for the W1 interface | IETF |
| R3-211042 | void | ETSI-MCC |
| R3-211050 | CB: # 82_SDT_LS - Summary of email discussion | Ericsson - moderator |
| R3-211051 | [DRAFT] Reply LS to RAN3 on small data transmission | Ericsson |
| R3-211052 | CB: # 83_DL_RRCsegmentation - Summary of email discussion | Ericsson - moderator |
| R3-211053 | [DRAFT] Reply LS on DL RRC segmentation | Ericsson |
| R3-211054 | [draft] Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-211138 | Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-211140 | Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-211280 | Reply LS on small data transmission | Ericsson |
| 8.2 | LSin received during the meeting | |
| R3-210698 | Discussion on Incoming LS on Rel-16 NR Positioning Correction | Huawei |
| R3-210699 | Including SRS frequency information Positioning Information Request | Huawei, Qualcomm Incorporated |
| R3-210700 | Including SRS frequency information Positioning Information Request | Huawei, Qualcomm Incorporated |
| R3-210950 | Discussion on positioning UL SRS Activation time | Ericsson LM |
| R3-210951 | Correction of NRPPa periodic UL SRS time transmission | Ericsson, ZTE |
| R3-210952 | Correction of F1AP periodic UL SRS time transmission | Ericsson, ZTE |
| R3-211162 | Reply LS on Rel-16 NR positioning Correction | RAN WG1 |
| R3-211163 | Including SRS frequency information in Positioning Information Request | Huawei, Qualcomm Incorporated |
| R3-211164 | Including SRS frequency information in Positioning Information Request | Huawei, Qualcomm Incorporated |
| 8.3.1 | QoS Monitoring for URLLC | |
| R3-210061 | Discussion on QoS monitoring control | ZTE Corporation |
| R3-210062 | Update on QoS monitoring control | ZTE Corporation |
| R3-210063 | Update on QoS monitoring control | ZTE Corporation |
| R3-210064 | Update on QoS monitoring control | ZTE Corporation |
| R3-210065 | Update on QoS monitoring control | ZTE Corporation |
| R3-210071 | LS on QoS monitoring control | ZTE Corporation |
| R3-210269 | Discussion on QoS Monitoring for URLLC | Samsung |
| R3-210426 | QoS monitoring for URLCC | Ericsson |
| R3-210427 | UE support for D1 part of UL Delay | Ericsson |
| R3-210428 | UE support for D1 part of UL Delay | Ericsson |
| R3-210434 | Open issues for RAN part delay reporting for Qos monitoring for URLLC | Huawei |
| R3-210435 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-210436 | D1 indication in RAN part delay reporting | Huawei |
| R3-210437 | [Draft] Reply on LS on Clarification on URLLC QoS Monitoring | Huawei |
| R3-210954 | CB: # 1_QoSmonURLLC - Summary of email discussion | Ericsson - moderator |
| R3-211188 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211215 | UE support for D1 part of UL Delay | Ericsson |
| R3-211224 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211225 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211226 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211276 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211277 | Update on QoS monitoring control | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211319 | Addition of D1 delay result | Nokia, Nokia Shanghai Bell |
| R3-211321 | UE support for D1 part of UL Delay | Ericsson |
| 8.3.2 | End Marker in NG-RAN Initiated QoS Flow Mobility | |
| R3-210058 | Correction of End markers and QoS Flow Mobility (MN to SN) | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210059 | Correction of Xn DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210060 | Correction of Xn DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210120 | DL end marker handling between MN and SN | Huawei, Deutsche Telekom |
| R3-210121 | DL end marker handling between MN and SN | Huawei, Deutsche Telekom |
| R3-210122 | DL end marker handling between MN and SN | Huawei, Deutsche Telekom |
| R3-210955 | CB: # 2_QoSflowMob_endmarkers - Summary of email discussion | Nokia - moderator |
| R3-211047 | Correction of Xn DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211048 | Correction of Xn DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell, Ericsson |
| 8.3.3 | SRS-RSRP Information Exchange | |
| R3-210853 | Left issue for CLI | ZTE |
| R3-210854 | CLI Notification between NG-RAN node | ZTE |
| R3-210855 | Response LS on SRS-RSRP | ZTE |
| R3-210956 | CB: # 3_SRS-RSRPinfo_xch - Summary of email discussion | ZTE - moderator |
| 8.3.5 | QoS Parameters Update at Xn Handover | |
| R3-210584 | Introducing QoS parameters update at Xn handover | Huawei, Ericsson, ZTE, CATT, Samsung |
| R3-210585 | Introducing QoS parameters update at Xn handover | Huawei, Ericsson, ZTE, CATT, Samsung |
| R3-210957 | CB: # 4_QoSupdate@XnHO - Summary of email discussion | Huawei - moderator |
| R3-211142 | Introducing QoS parameters update at Xn handover | Huawei, Ericsson, ZTE, CATT, Samsung |
| R3-211257 | CB: # 4_QoSupdate@XnHO - Summary of email discussion | Huawei - moderator |
| R3-211258 | Introducing QoS parameters update at Xn handover | Huawei, Ericsson, ZTE, CATT, Samsung |
| 8.3.6 | Support for Full Slot Formats in TDD | |
| R3-210032 | Reply LS on Full slot formats support in TDD UL-DL configuration | RAN WG2 |
| R3-210334 | Full slot format support in intended TDD UL-DL configuration | Qualcomm Incorporated, ZTE |
| R3-210433 | Half Slot Format Support for Intended TDD UL-DL Configuration | ZTE,Qualcomm Incorporated |
| R3-210501 | Discussion on full slot formats support in TDD UL-DL configuration | Huawei |
| R3-210958 | CB: # 5_FullSlotTDD - Summary of email discussion | Qualcomm - moderator |
| R3-211024 | Response to R3-210433 and R3-210334 | Ericsson |
| 9.2.1 | RAT Type Handling | |
| R3-210123 | Consideration on RAT Type Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom |
| R3-210124 | Correction on RAT Information Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom |
| R3-210125 | Correction on RAT Type Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom |
| R3-210126 | Supported RATs of the AMF | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom |
| R3-210127 | Supported RATs of the MME | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, Verizon Wireless |
| R3-210204 | Consideration on RAT Type Handling | ZTE |
| R3-210959 | CB: # 6_RATtypeHandling - Summary of email discussion | Huawei - moderator |
| R3-211023 | Response to R3-210123 | Ericsson |
| R3-211191 | Correction on RAT Information Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| R3-211192 | Correction on RAT Type Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| R3-211193 | Supported RATs of the AMF | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| R3-211194 | Supported RATs of the MME | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| R3-211250 | Correction on RAT Information Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| R3-211251 | Correction on RAT Type Handling | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless |
| 9.2.2 | Others | |
| R3-210054 | Correction of IMS voice EPS fallback | Nokia, Nokia Shanghai Bell |
| R3-210055 | Correction of IMS voice Emergency Indicator | Nokia, Nokia Shanghai Bell |
| R3-210197 | Consideration on the UE identity index for eMTC UE in RRC_INACTIVE | ZTE, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210198 | Correction on UE identity index for eMTC UE in RRC_INACTIVE | ZTE, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210199 | Correction on UE identity index for eMTC UE in RRC_INACTIVE | ZTE, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-210205 | Discussion on the UE information delivery for RRC_INACTIVE UE | ZTE, Qualcomm |
| R3-210206 | Correction on the DRX information delivery for RRC_INACTIVE UE | ZTE, Qualcomm |
| R3-210498 | Discussion on ciphering key discrepancy issue for legacy S1-handover | NTT DOCOMO, INC. |
| R3-210889 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-210890 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-210891 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211041 | Correction on the DRX information delivery for RRC_INACTIVE UE | ZTE, Qualcomm Incorporated, Ericsson |
| R3-211055 | CB: # 85_DRXinfo_delivery_inactive - Summary of email discussion | ZTE - moderator |
| R3-211056 | Correction on the DRX information delivery for RRC_INACTIVE UE | ZTE, Qualcomm Incorporated, Ericsson |
| R3-211057 | CB: # 86_S1ciphering_discrepancy - Summary of email discussion | NTT Docomo - moderator |
| R3-211058 | CB: # 87_IMSvoiceEPS_fallback_X2 - Summary of email discussion | Nokia - moderator |
| R3-211059 | CB: # 88_IMSvoice_emergency_indicator - Summary of email discussion | Nokia - moderator |
| R3-211060 | CB: # 89_E-RABs_that_cannot_be_handed_over - Summary of email discussion | Ericsson - moderator |
| R3-211088 | E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211096 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211182 | Correction on Paging DRX information for RRC_INACTIVE UE | Nokia, Nokia Shanghai Bell |
| R3-211204 | LS on emergency Indicator in Emergency Fallback | Nokia, Nokia Shanghai Bell |
| R3-211244 | Correction of IMS voice Emergency Indicator | Nokia, Nokia Shanghai Bell |
| R3-211273 | E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211315 | Correction on the DRX information delivery for RRC_INACTIVE UE | ZTE, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-211317 | Correction on Paging DRX information for RRC_INACTIVE UE | Nokia, Nokia Shanghai Bell |
| 9.3.2 | Overlapping Band Handling in F1AP | |
| R3-210033 | Reply LS on band selection and indication on single connectivity | RAN WG2 |
| R3-210066 | Correction on Overlapping Band Handling over F1 | ZTE |
| R3-210067 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-210068 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-210142 | Discussion on Overlapping Bands | Nokia, Nokia Shanghai Bell |
| R3-210324 | Overlapping bands handling | Ericsson, Verizon Wireless |
| R3-210325 | Overlapping band handling CR 38.473 | Ericsson, Verizon Wireless |
| R3-210326 | Overlapping band handling CR 38.473 | Ericsson, Verizon Wireless |
| R3-210810 | Further discussions on frequency band overlapping | Huawei |
| R3-210960 | CB: # 7_OverlappingBandsF1AP - Summary of email discussion | ZTE - moderator |
| R3-211083 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| R3-211160 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| R3-211291 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| R3-211292 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC |
| 9.3.3 | AS-Rekey and Emergency Fallback | |
| R3-210046 | Correction of AS Rekeying and Emergency Fallback | Nokia, Nokia Shanghai Bell |
| R3-210047 | Correction of AS Rekeying and Emergency Fallback | Nokia, Nokia Shanghai Bell |
| R3-210048 | Correction of AS Rekeying and Emergency Fallback | Nokia, Nokia Shanghai Bell |
| R3-210128 | Consideration on AS-rekey and Emergency fallback | Huawei |
| R3-210129 | Correction on AS-rekey and Emergency fallback | Huawei |
| R3-210130 | Correction on AS-rekey and Emergency fallback | Huawei |
| R3-210327 | AS re-keying and Emergency Fallback in the UE Context Modification procedure | Ericsson |
| R3-210328 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson, ZTE |
| R3-210329 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson, ZTE |
| R3-210330 | Draft] Reply LS on AS rekeying handling | Ericsson |
| R3-210466 | Discussion on AS rekey and Emergency fallback | CATT |
| R3-210467 | Correction on collision of AS-rekey and Emergency fallback_NGAP Rel-15 | CATT |
| R3-210468 | Correction on collision of AS-rekey and Emergency fallback_NGAP Rel-16 | CATT |
| R3-210961 | CB: # 8_AS_rekey_emergency_fallback - Summary of email discussion | Ericsson - moderator |
| R3-211171 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, CATT |
| R3-211172 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, CATT |
| 9.3.4.1 | E1 Aspects | |
| R3-210155 | Solution for 4g-5g direct data forwarding | Nokia, Nokia Shanghai Bell |
| R3-210156 | Support of 4g-5g direct data forwarding over E1 | Nokia, Nokia Shanghai Bell |
| R3-210255 | Direct data forwarding for inter-system HO from 4G to 5G with a shared split (S)gNB | Samsung, LGU+ |
| R3-210256 | Support of direct data forwarding for inter-system HO from 4G to 5G with a shared split (S)gNB | Samsung, LGU+ |
| R3-210656 | CR to TS38.463 on Support of direct data forwarding for inter-system HO | China Telecom, CATT, ZTE |
| R3-210691 | Support of direct data forwarding for inter-system HO | CATT, China Telecom, ZTE |
| R3-210692 | Support of inter-node handover with a shared split (S)gNB | CATT, China Telecom, ZTE |
| R3-210741 | Inter-system HO with shared CU-UP | Ericsson |
| R3-210962 | CB: # 9_DirectDataFwd_E1 - Summary of email discussion | Nokia - moderator |
| R3-211169 | Support of 4g-5g direct data forwarding over E1 | Nokia, Nokia Shanghai Bell |
| R3-211293 | CB: # 9_DirectDataFwd_E1 - Summary of email discussion | Nokia - moderator |
| 9.3.4.2 | With Mobility Between DC and SA | |
| R3-210247 | Discussion on inter-system handover from EN-DC to SA | CATT, China Telecom,Qualcomm, CMCC |
| R3-210248 | Support of direct data forwarding for S-NG-RAN node change or NR-NR DC to SA handover | China Telecom,CATT |
| R3-210249 | CR for 36.423 Support of direct data forwarding for EN-DC to SA | CATT, China Telecom |
| R3-210335 | SN direct data forwarding | Qualcomm Incorporated, CATT, China Telecom |
| R3-210336 | SN direct data forwarding | Qualcomm Incorporated, CATT |
| R3-210337 | SN direct data forwarding | Qualcomm Incorporated, CATT |
| R3-210586 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung |
| R3-210786 | Direct data forwarding for handover without O&M configuraiton | Samsung, Huawei |
| R3-210963 | CB: # 10_DirectDataFwd_DC-CAmobility - Summary of email discussion | Qualcomm - moderator |
| 9.3.4.3 | PDCP SN Handling for EPC to 5GC HO | |
| R3-210088 | Enabling direct data forwarding for inter-RAT HO with SN-terminated bearers | Nokia, Nokia Shanghai Bell |
| R3-210450 | PDCP SN issue for EPC to 5GC handover | Huawei, CATT |
| R3-210451 | PDCP SN issue for EPC to 5GC handover | Huawei, CATT |
| R3-210742 | PDCP SNs for forwarded PDCP SDUs from 4G to 5G | Ericsson |
| R3-210743 | Inter-system indicator for Bearer Context Setup | Ericsson |
| R3-210806 | PDCP SN Handling for EPC to 5GC HO | Samsung |
| R3-210840 | PDCP SN Handling for EPC to 5GC HO | Samsung |
| R3-210964 | CB: # 11_DirectDataFwd_PDCP_SN_4G-5G_HO - Summary of email discussion | Huawei - moderator |
| R3-211206 | PDCP SN issue for EPC to 5GC handover | Huawei, CATT |
| 9.3.5 | LTE-NR Relative Timing Indication | |
| R3-210232 | Discussion on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE, CATT |
| R3-210233 | CR to TS36.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-210235 | CR to TS38.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-210372 | Introduction of SFN Offset per NR cell | Ericsson |
| R3-210373 | Introduction of SFN Offset per NR cell | Ericsson |
| R3-210374 | Introduction of SFN Offset per NR cell | Ericsson |
| R3-210418 | Discussion on SFN0 offset signalling between LTE and NR | Ericsson |
| R3-210811 | Further discussion on LTE-NR timing information exchange over eNB and gNB | Huawei |
| R3-210812 | CR to 36.423 on LTE-NR timing information exchange over eNB and gNB | Huawei |
| R3-210813 | CR to 38.423 on LTE-NR timing information exchange over eNB and gNB | Huawei |
| R3-210965 | CB: # 12_LTE-NR RelTiming - Summary of email discussion | Ericsson - moderator |
| R3-211091 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211092 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211093 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211282 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211283 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211284 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE |
| R3-211288 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE, Qualcomm |
| R3-211289 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE, Qualcomm |
| R3-211290 | Introduction of SFN Offset per NR cell | Ericsson, China Telecom, ZTE, Qualcomm |
| R3-211322 | Introduction of SFN Offset per cell over X2 | Ericsson, China Telecom, ZTE, Qualcomm |
| R3-211323 | Introduction of SFN Offset per cell over Xn | Ericsson, China Telecom, ZTE |
| R3-211324 | Introduction of SFN Offset per cell over F1 | Ericsson, China Telecom, ZTE, Qualcomm |
| 9.3.6 | Lossless Intra-System HO in CP-UP Separation Scenario | |
| R3-210146 | Discussion on Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-210147 | Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-210252 | Lossless intra-system HO in disaggregate gNB scenario | Samsung, Huawei, LGU+, China Telecom, Intel Corporation |
| R3-210253 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, LGU+, China Telecom, Intel Corporation |
| R3-210254 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, LGU+, China Telecom, Intel Corporation |
| R3-210290 | Support of data forwarding for intra-system HO in CP-UP Separation Scenario | CATT |
| R3-210797 | Discussion on Lossless Intra-system HO in CP-UP Separation Scenario | ZTE |
| R3-210966 | CB: # 13_LosslessIntraSysHO_CP-UPsplit - Summary of email discussion | Samsung - moderator |
| R3-211081 | Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-211259 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, LGU+, China Telecom, Intel Corporation |
| R3-211260 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, LGU+, China Telecom, Intel Corporation |
| R3-211294 | CB: # 13_LosslessIntraSysHO_CP-UPsplit - Summary of email discussion | Samsung - moderator |
| 9.3.7 | Mobility Restrictions in SN Addition | |
| R3-210095 | Mobility Restrictions in S-Node Addition | Nokia, Nokia Shanghai Bell |
| R3-210096 | Clarification of 5GC Mobility Restriction List Container | Nokia, Nokia Shanghai Bell |
| R3-210097 | Clarification of EPC Handover Restriction List Container | Nokia, Nokia Shanghai Bell |
| R3-210131 | Consideration on MRL in SN Addition Procedure | Huawei |
| R3-210132 | Introduce 5GC Mobility Restriction List Container in DC | Huawei |
| R3-210133 | Introduce 5GC Mobility Restriction List Container in DC | Huawei |
| R3-210134 | Introduce EPC Handover Restriction List Container in EN-DC | Huawei |
| R3-210135 | Introduce EPC Handover Restriction List Container in EN-DC | Huawei |
| R3-210634 | Necessary corrections on the usage of the 5GC MRL Container IE on Xn | Ericsson |
| R3-210635 | Correction related to the 5GC Mobility Restriction List Container | Ericsson |
| R3-210636 | Correction related to the 5GC Mobility Restriction List Container | Ericsson |
| R3-210967 | CB: # 14_MobRestr_SNadd - Summary of email discussion | Nokia - moderator |
| R3-211218 | Clarification of 5GC Mobility Restriction List Container | Nokia, Nokia Shanghai Bell |
| R3-211219 | Clarification of EPC Handover Restriction List Container | Nokia, Nokia Shanghai Bell |
| 9.3.8 | Others | |
| R3-210710 | Rapporteur CR for XnAP | Ericsson |
| R3-210711 | Rapporteur CR for XnAP | Ericsson |
| R3-210747 | Rapporteur CR for X2AP | Ericsson |
| R3-210748 | Rapporteur CR for X2AP | Ericsson |
| 9.3.8.1 | Other Corrections | |
| R3-210049 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-210050 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-210051 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-210052 | Correction Ethernet Compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-210053 | LS on Synchronization of Ethernet compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-210074 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-210075 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-210098 | Correction on Abnormal Conditions in Handover Preparation Procedure for R15 | CATT |
| R3-210099 | Correction on Abnormal Conditions in Handover Preparation Procedure for R16 | CATT |
| R3-210116 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-210117 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-210118 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-210143 | Discussion on UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-210144 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-210145 | PLMN Not Supported Cause Value | Nokia, Nokia Shanghai Bell |
| R3-210150 | Correction to NRPPa Transport procedure description | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-210157 | Correction of Voice fallback triggered by Initial Context Setup | Nokia, Nokia Shanghai Bell, TMO US, Orange, Qualcomm Incorporated |
| R3-210158 | Correction of Voice fallback triggered by Initial Context Setup | Nokia, Nokia Shanghai Bell, TMO US, Orange, Qualcomm Incorporated |
| R3-210212 | Correction on transmission stop for Rel-16 DAPS | Samsung, Intel Corporation, CATT |
| R3-210213 | Stage-2 CR on transmission stop for Rel-16 DAPS handover | Samsung, Intel Corporation, CATT |
| R3-210214 | Stage-3 CR on transmission stop for Rel-16 DAPS handover | Samsung, Intel Corporation, CATT |
| R3-210229 | Correction of S-NODE MODIFICATION REQUEST ACKNOWLEDGE message | Samsung, ZTE, Huawei |
| R3-210230 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-210231 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-210236 | UL Configuration handling in MR-DC | NEC, ZTE |
| R3-210237 | Correction on UL Configuration handling | NEC, ZTE |
| R3-210238 | Correction on UL Configuration handling | NEC, ZTE |
| R3-210286 | Discard NR PDCP PDUs without PDCP PDU transfer | Huawei, Deutsche Telekom, China Unicom |
| R3-210287 | Discard NR PDCP PDUs without PDCP PDU transfer | Huawei, Deutsche Telekom, China Unicom |
| R3-210300 | Clarification on trigger condition for trace Failure Indication procedure | CATT,China Telecom |
| R3-210301 | Clarification on multiple Trace Start procedure | CATT |
| R3-210303 | Correction on UE History Information | CATT |
| R3-210304 | Correction on LTE UE RLF Report | CATT |
| R3-210305 | Correction on PRACH coordination | CATT, Huawei,CMCC |
| R3-210331 | Discussion and solution on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-210338 | Use of the UE’s Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, ZTE |
| R3-210339 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, ZTE |
| R3-210340 | SN indication in resume from different MN | Qualcomm Incorporated |
| R3-210341 | SN indication in UE context retrieval | Qualcomm Incorporated |
| R3-210342 | Remaining BSR transfer in handover | Qualcomm Incorporated |
| R3-210343 | Remaining BSR transfer in handover | Qualcomm Incorporated |
| R3-210370 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-210371 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-210375 | Measurement gap deactivation over F1AP | Ericsson, Verizon Wireless |
| R3-210376 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Verizon Wireless |
| R3-210377 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Verizon Wireless |
| R3-210378 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-210379 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-210380 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-210382 | MRO Inter-system measurement Configuration | Ericsson |
| R3-210384 | MRO S1AP clarifications for Inter-system measurement Configuration | Ericsson |
| R3-210385 | Transparent signalling of MeasGapConfig IE at gNB-CU | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-210386 | Transparent signalling of MeasGapConfig IE at gNB-CU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-210387 | Transparent signalling of MeasGapConfig IE at gNB-CU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-210406 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-210407 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-210408 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-210409 | Cause value on X2, Xn and F1 for insufficient UE capabilities | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210410 | Cause value on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210411 | Cause value on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210412 | Cause value on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210413 | Cause value on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210414 | Cause value on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210416 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210419 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-210420 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-210421 | Correction of Emergency PDU Session | Nokia, Nokia Shanghai Bell, AT&T, Verizon Wireless |
| R3-210431 | SCell Information from gNB-DU | Nokia, Nokia Shanghai Bell |
| R3-210432 | SCell Information from gNB-DU | Nokia, Nokia Shanghai Bell |
| R3-210438 | Support of dynamic ACL during handover and dual connectivity | Huawei |
| R3-210439 | Support of dynamic ACL during handover and dual connectivity | Huawei |
| R3-210440 | Support of dynamic ACL during handover and dual connectivity | Huawei |
| R3-210452 | Correction of NPN related Cell Information | Huawei, China Telecom |
| R3-210453 | Correction of NPN related Cell Information | Huawei, China Telecom |
| R3-210454 | Support of shared-DU and dedicated logical-CU for NPN | Huawei, China Telecom |
| R3-210455 | Correction of Allocated C-RNTI for 2-step RACH | Huawei, CMCC |
| R3-210456 | Discussion on the size limitation of DTLS over SCTP | Huawei, China Telecom |
| R3-210457 | Discussion on the size limitation of DTLS over SCTP | Huawei, China Telecom |
| R3-210469 | CR for 38.455 Correction of Positioning SRS Resource | CATT |
| R3-210484 | Discussion on NG-RAN node behaviour when it receives the Xn Signalling TNL association address at source NG-C side IE | Nokia, Nokia Shanghai Bell, China Telecom, Huawei |
| R3-210485 | Clarify NG-RAN node behavior upon the reception of the Signalling TNL association address at source NG-C side IE | Nokia, Nokia Shanghai Bell, China Telecom, Huawei |
| R3-210486 | Clarify NG-RAN node behavior upon the reception of the Signalling TNL association address at source NG-C side IE | Nokia, Nokia Shanghai Bell, China Telecom, Huawei |
| R3-210543 | Correction on BAP configuration | Huawei |
| R3-210544 | Correction on BAP address configuration for IAB-donor-DU | Huawei, LG Electronics, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-210545 | Correction on clarification of non-F1 traffic | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-210546 | Correction on IAB procedures | Huawei, ZTE |
| R3-210571 | Max number of supported AMF Regions exceeded at NG-RAN node | ZTE, China Unicom, China Telecom |
| R3-210572 | Rel-15 CR Max number of supported AMF Regions exceeded at NG-RAN node | ZTE, China Unicom, China Telecom |
| R3-210573 | Rel-16 CR Max number of supported AMF Regions exceeded at NG-RAN node | ZTE, China Unicom, China Telecom |
| R3-210574 | MDT for Inactive UEs | ZTE, Samsung, Qualcomm Incorporated |
| R3-210575 | PCR for Signalling based logged MDT for UE in RRC_INACTIVE state | ZTE, Samsung, Qualcomm Incorporated |
| R3-210576 | LS-out MDT for Inactive UEs | ZTE, Samsung, Qualcomm Incorporated |
| R3-210577 | NGAP cause value for UE context transfer_R15 | ZTE,China Telecom |
| R3-210578 | NGAP cause value for UE context transfer_R16 | ZTE,China Telecom |
| R3-210579 | XnAP cause value for UE context transfer_R15 | ZTE,China Telecom |
| R3-210580 | XnAP cause value for UE context transfer_R16 | ZTE,China Telecom |
| R3-210581 | Correction on MDT location information on NGAP | ZTE,China Telecom |
| R3-210582 | Correction on MDT location information on F1AP | ZTE,China Telecom |
| R3-210587 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei, CMCC |
| R3-210588 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei, CMCC |
| R3-210589 | Correction of S-NSSAI in served cell information | Huawei, CATT, Lenovo , Motorola Mobility |
| R3-210590 | Correction of S-NSSAI in served cell information | Huawei, CATT, Lenovo , Motorola Mobility |
| R3-210591 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom |
| R3-210592 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom |
| R3-210593 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-210594 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-210595 | Direct forwarding path availability in Handover Required message | Huawei, CATT |
| R3-210596 | Direct forwarding path availability in Handover Required message | Huawei, CATT |
| R3-210624 | Cause value on X2, Xn for normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210625 | Cause value on Xn for normal release CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210626 | Cause value on Xn for normal release CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210627 | Cause value on X2 for normal release CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210628 | Cause value on X2 for normal release CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210655 | Correction of NG-AP Suspend Request | Ericsson |
| R3-210668 | F1AP correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell |
| R3-210669 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell |
| R3-210670 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell |
| R3-210701 | Corrections on NRPPa | Huawei, Ericsson, Nokia |
| R3-210712 | CR to 38.473: Miscellaneous corrections on V2X | ZTE, LG |
| R3-210713 | CR to 38.460: Supporting IAB function and procedure | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-210714 | CR to 38.473: Correction on UE Context Modification Required procedure | ZTE, KDDI Corporation, Nokia, Nokia Shanghai Bell |
| R3-210715 | CR to 38.473: Correction on IAB related definitions and unsuccessful establishment of a BH RLC channel | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-210720 | CR TS 38.473: HSNA Configuration per (Parent-DU) Cell Serving the Collocated IAB-MT | Ericsson, AT&T, KDDI |
| R3-210727 | Maximum Number of RRC connections | Ericsson, CMCC |
| R3-210737 | Including the Redundant UL NG-U UP TNL Information in the Modify Request | Ericsson, CATT, ZTE |
| R3-210738 | Including the Redundant UL NG-U UP TNL Information in the Modify Request | Ericsson, CATT, ZTE |
| R3-210739 | UL primary path signaling over E1 | Ericsson |
| R3-210740 | UL primary path signaling over E1 | Ericsson |
| R3-210761 | Correction CR on Network instance for 38.413(R15) | CATT |
| R3-210762 | Correction CR on DAPS Response Information | CATT |
| R3-210763 | Issue of intra gNB-CU-UP DAPS HO | CATT |
| R3-210764 | CR to TS 38463 for Intra gNB-CU-UP DAPS HO | CATT |
| R3-210794 | Correction of last PDU session release for SSC mode 2 | Huawei |
| R3-210814 | Discussion on NG interface failure indication between 4G and 5G | Huawei |
| R3-210815 | Discussion on Inactive timer transfer | Huawei, China Unicomm |
| R3-210816 | CR to 38.473 on introduction of the IE ue-InactiveTime | Huawei, China Unicomm |
| R3-210817 | CR to 38.473 on introduction of the IE ue-InactiveTime | Huawei, China Unicomm |
| R3-210818 | CR to 38.463 on introduction of the IE ue-InactiveTime | Huawei, China Unicomm |
| R3-210819 | CR to 38.463 on introduction of the IE ue-InactiveTime | Huawei, China Unicomm |
| R3-210823 | CR for TS38.401 on Signalling based MDT Activation | ZTE, China Telecom |
| R3-210824 | Discussion on RAN Sharing Enhancement for MLB in NR | ZTE, China Telecom, China Unicom |
| R3-210825 | CR for TS38.300 on RAN Sharing Enhancement for MLB | ZTE, China Telecom, China Unicom |
| R3-210828 | CR for TS38.423 on RAN Sharing Enhancement for MLB | ZTE, China Telecom, China Unicom |
| R3-210830 | Discussion on Enhancement of MLB in Rel-16 | ZTE, China Telecom, China Unicom |
| R3-210831 | Correction of the DAPS Response Information IE in the tabular | Samsung |
| R3-210833 | CR for TS38.423 on Enhancement of MLB in Rel-16 | ZTE, China Telecom, China Unicom |
| R3-210834 | Clarification on the DAPS HO response per E-RABs | Samsung |
| R3-210835 | Clarification on the DAPS HO response per DRBs | Samsung |
| R3-210836 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-210837 | CR for TS38.473 on Enhancement of MLB in Rel-16 | ZTE, China Telecom, China Unicom |
| R3-210838 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-210841 | CR to 38.463 Correction on IAB UP TNL Address Update | ZTE, Samsung, CATT |
| R3-210856 | Editorial corrections on IE type and reference in tabular for TS38.423 | ZTE Corporation |
| R3-210858 | Support of dynamic ACL during handover and dual connectivity | Huawei, China Telecom |
| R3-210859 | Support of dynamic ACL during handover and dual connectivity | Huawei, China Telecom |
| R3-210860 | Support of dynamic ACL during handover and dual connectivity | Huawei,China Telecom |
| R3-210871 | CR to 37.473 on miscellaneous corrections | Huawei, China Unicomm, Orange, TIM |
| R3-210872 | CR to 37.473 on MeasGapSharingConfig | Huawei, China Unicomm |
| R3-210882 | [Draft] LS on last PDU session release for SSC mode 2 | Huawei |
| R3-210883 | Rejected PSCell on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210884 | Rejected PSCell on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210885 | Rejected PSCell on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210886 | Rejected PSCell on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210887 | Rejected PSCell on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210888 | Rejected PSCell on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-210892 | Remove the user message size limitation over DTLS/SCTP | Ericsson |
| R3-210893 | [DRAFT] Remove the user message size limitation over DTLS/SCTP | Ericsson |
| R3-210936 | Correction for CHO early data forwarding in MN to eNB/gNB Change | Intel Corporation, Samsung |
| R3-210937 | 36.423 correction for CHO early data forwarding in MN to eNB Change scenario | Intel Corporation, Samsung |
| R3-210938 | 38.423 correction for CHO early data forwarding in MN to ng-eNB/gNB Change scenario | Intel Corporation, Samsung |
| R3-210939 | 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario | Intel Corporation, Samsung |
| R3-210940 | 37.340 correction for CHO early data forwarding in MN to eNB/gNB Change scenario | Intel Corporation, Samsung |
| R3-210941 | X2AP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-210942 | XnAP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-210968 | CB: # 15_IAB_Rel16Corrections - Summary of email discussion | Qualcomm - moderator |
| R3-211045 | Correction of the PCI IE presence in the ASN.1 for the SRS Configuration | Huawei |
| R3-211046 | CR to 38.473: Miscellaneous corrections on V2X | ZTE, LG, Google |
| R3-211061 | Corrections on NRPPa | Huawei, Ericsson, Nokia, Qualcomm |
| R3-211062 | CB: # 90_MOACV - Summary of email discussion | Ericsson - moderator |
| R3-211063 | CB: # 91_MOACV2 - Summary of email discussion | Ericsson - moderator |
| R3-211064 | Cause value on X2, Xn and F1 for insufficient UE capabilities | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211065 | Cause value on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211066 | Cause value on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211067 | Cause value on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211068 | Cause value on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211069 | Cause value on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211070 | Cause value on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211071 | Rejected PSCell on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211072 | Rejected PSCell on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211073 | Rejected PSCell on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211074 | Rejected PSCell on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211075 | Rejected PSCell on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211076 | Rejected PSCell on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211079 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-211080 | PLMN Not Supported Cause Value | Nokia, Nokia Shanghai Bell |
| R3-211082 | SCell Information from gNB-DU | Nokia, Nokia Shanghai Bell |
| R3-211089 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-211090 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-211094 | MRO S1AP clarifications for Inter-system measurement Configuration | Ericsson |
| R3-211097 | CB: # 92_Voice_fallback_initCtxtSetup - Summary of email discussion | Nokia - moderator |
| R3-211098 | Discard NR PDCP PDUs without PDCP PDU transfer | Huawei, Deutsche Telekom, China Unicom |
| R3-211099 | CB: # 94_MeasGapConfig_signaling - Summary of email discussion | Ericsson - moderator |
| R3-211100 | Correction on PRACH coordination | CATT, Huawei,CMCC |
| R3-211101 | CB: # 95_DAPS_HO_TXstop - Summary of email discussion | Samsung - moderator |
| R3-211102 | Stage-2 CR on transmission stop for Rel-16 DAPS handover | Samsung, Intel Corporation, CATT |
| R3-211103 | Stage-3 CR on transmission stop for Rel-16 DAPS handover | Samsung, Intel Corporation, CATT |
| R3-211104 | CB: # 96_SNmodAck - Summary of email discussion | Samsung - moderator |
| R3-211105 | CB: # 97_SignalingTNLassocAddr - Summary of email discussion | Nokia - moderator |
| R3-211106 | draft LS to SA2 | Nokia |
| R3-211107 | CB: # 98_DTLSsize_limit - Summary of email discussion | Ericsson - moderator |
| R3-211108 | [DRAFT] Remove the user message size limitation over DTLS/SCTP | Ericsson |
| R3-211109 | CB: # 99_MaxAMFregions - Summary of email discussion | ZTE - moderator |
| R3-211110 | CB: # 100_MDTinactiveUEs - Summary of email discussion | ZTE - moderator |
| R3-211111 | CB: # 101_SecondaryRAT - Summary of email discussion | Huawei - moderator |
| R3-211112 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-211113 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-211114 | CB: # 102_RedundantUL_NG-U_UP_TNLinfo - Summary of email discussion | Ericsson - moderator |
| R3-211115 | CB: # 103_RANsharingMLB - Summary of email discussion | ZTE - moderator |
| R3-211116 | CB: # 104_TraceFailTriggering - Summary of email discussion | CATT - moderator |
| R3-211117 | CB: # 105_ULconfigHandling - Summary of email discussion | NEC - moderator |
| R3-211118 | Correction on UL Configuration handling | NEC, ZTE |
| R3-211119 | Correction on UL Configuration handling | NEC, ZTE |
| R3-211122 | CB: # 106_PCIrecnonfig - Summary of email discussion | Ericsson - moderator |
| R3-211123 | CB: # 107_SNPNfailure - Summary of email discussion | Nokia - moderator |
| R3-211124 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-211125 | CB: # 108_NR-NR_DCconfigRelease - Summary of email discussion | Ericsson - moderator |
| R3-211126 | CB: # 109_ARPcorrection - Summary of email discussion | Nokia - moderator |
| R3-211127 | CB: # 110_EthernetCompressionSync - Summary of email discussion | Nokia - moderator |
| R3-211128 | LS on Synchronization of Ethernet compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-211129 | Correction of NPN related Cell Information | Huawei, China Telecom |
| R3-211130 | Correction of NPN related Cell Information | Huawei, China Telecom |
| R3-211139 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-211143 | Correction on clarification of non-F1 traffic | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-211144 | Correction on IAB procedures | Huawei, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-211156 | CR to 38.460: Supporting IAB function and procedure | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-211157 | CR to 38.473: Correction on IAB related definitions and unsuccessful establishment of a BH RLC channel | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-211158 | CR to 38.463 Correction on IAB UP TNL Address Update | ZTE, Samsung, CATT |
| R3-211181 | Correction of Voice fallback triggered by Initial Context Setup | Nokia, Nokia Shanghai Bell, TMO US, Orange, Qualcomm Incorporated |
| R3-211183 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-211184 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-211197 | Including the Redundant UL NG-U UP TNL Information in the Modify Request | Ericsson, CATT, ZTE |
| R3-211198 | Including the Redundant UL NG-U UP TNL Information in the Modify Request | Ericsson, CATT, ZTE |
| R3-211245 | Cause value on Xn for insufficient UE capabilities CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211246 | Cause value on F1 for insufficient UE capabilities CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211247 | Cause value on X2 for insufficient UE capabilities CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone, NTT Docomo |
| R3-211248 | Cause value on Xn for normal release CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-211249 | Cause value on X2 for normal release CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC, BT, AT&T, China Unicom, Telecom Italia, Vodafone |
| R3-211253 | Clarification on trigger condition for trace Failure Indication procedure | CATT,China Telecom |
| R3-211254 | Clarification on trigger condition for trace Failure Indication procedure | CATT,China Telecom |
| R3-211256 | LS on TRACE procedure | CATT |
| R3-211262 | CR to 38.460: Supporting IAB function and procedure | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-211263 | CR to 38.473: Correction on IAB related definitions and unsuccessful establishment of a BH RLC channel | ZTE, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-211264 | CR to 38.463 Correction on IAB UP TNL Address Update | ZTE, Samsung, CATT |
| R3-211267 | Correction on UL Configuration handling | NEC, ZTE |
| R3-211268 | Correction on UL Configuration handling | NEC, ZTE |
| R3-211269 | CB: # 105_ULconfigHandling - Summary of email discussion | NEC - moderator |
| R3-211271 | Signalling based logged MDT for UE in RRC_INACTIVE | Samsung |
| R3-211274 | Remove the user message size limitation over DTLS/SCTP | Ericsson |
| R3-211287 | PCR for Signalling based logged MDT for UE in RRC_INACTIVE state | ZTE, Samsung, Qualcomm Incorporated |
| R3-211299 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-211300 | Correction of SN modification request ack message | Samsung, ZTE, Huawei |
| R3-211310 | Stage-3 CR on transmission stop for Rel-16 DAPS handover | Samsung, Intel Corporation, CATT |
| R3-211311 | CB: # 95_DAPS_HO_TXstop - Summary of email discussion | Samsung - moderator |
| R3-211313 | Signalling based logged MDT for UE in RRC_INACTIVE | Samsung |
| R3-211325 | LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | Ericsson |
| R3-211345 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-211346 | Clarification of Secondary RAT in mobility restrictions | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-211359 | LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | Ericsson |
| R3-211361 | CR to 37.473 on miscellaneous corrections | Huawei, China Unicomm, Orange, TIM |
| 9.3.8.2 | Pure Stage-2 Corrections | |
| R3-210069 | Correction on NGAP functions | ZTE Corporation |
| R3-210070 | Correction on NGAP functions | ZTE Corporation |
| R3-210115 | Support of RAN sharing for the disaggregated SNPN | China Telecommunication |
| R3-210250 | Issues in stage 2 on MRO | Samsung, CMCC, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-210251 | Correction of MRO in stage 2 | Samsung, CMCC, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-210302 | Correction on detection mechanisms for Intra-system too late handover | CATT,CMCC,ZTE |
| R3-210430 | Correction on conditional reconfiguration for PSCell | Google Inc., Intel Corporation, CATT |
| R3-210522 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-210523 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-210611 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| R3-210612 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| R3-210613 | RRC Re-establishment and inter-vendor CU operation | Ericsson, Verizon Wireless, CMCC |
| R3-210702 | Discussion on NRPPa transaction types | Huawei |
| R3-210943 | Clean-up on Xn-U Address Indication procedure | Intel Corporation |
| R3-210944 | Clean-up on Xn-U Address Indication procedure | Intel Corporation |
| R3-211095 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| 10.1 | General | |
| R3-210006 | BLCR to 36.423:Support of MDT enhancement | CATT |
| R3-210007 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-210008 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-210009 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-210010 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-210011 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-210012 | MDT in MR-DC | Huawei |
| R3-210013 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-210018 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-210019 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| R3-210927 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-210988 | CB: # 1000_SONMDT_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-211085 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-211347 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-211348 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-211349 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-211350 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-211353 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-211354 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-211355 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| 10.2.1.1 | PCI Selection | |
| R3-210441 | (TP for SON BL CR for TS 38.300):Further clarification on distributed PCI selection | Huawei |
| R3-210989 | CB: # 1001_SONMDT_PCISelect - Summary of email discussion | Huawei - moderator |
| R3-211159 | (TP for SON BL CR for TS 38.300):Further clarification on distributed PCI selection | Huawei |
| R3-211161 | (TP for SON BL CR for TS 38.300):Further clarification on distributed PCI selection | Huawei, Ericsson |
| 10.2.1.3 | Successful Handover Report | |
| R3-210111 | (TP for SON BLCR 38.473) Introducing UE Assistant Identifier in F1AP for Successful HO Report | China Telecommunication |
| R3-210672 | Successful Handover Report for CHO and DAPS | Ericsson |
| R3-210990 | CB: # 1002_SONMDT_SuccessHO - Summary of email discussion | China Telecom - moderator |
| R3-211165 | CB: # 1002_SONMDT_SuccessHO - Summary of email discussion | China Telecom - moderator |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-210079 | Solution for handling of the SCG UE history information | Nokia, Nokia Shanghai Bell |
| R3-210080 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-210081 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-210109 | Discussion on UE history information | China Telecommunication |
| R3-210264 | TP for SON BLCR for 38.423: UE History Information in EN-DC | Samsung |
| R3-210265 | TP for SON BLCR for 36.423: UE History Information in EN-DC | Samsung |
| R3-210297 | Enhancement of UE history information in MR-DC scenario | CATT |
| R3-210298 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT |
| R3-210299 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT |
| R3-210344 | UE History Information in MR-DC | Qualcomm Incorporated |
| R3-210391 | (TP for SON BLCR for 38.423) UE History Information in MR-DC | Huawei |
| R3-210392 | (TP for SON BLCR for 38.413) UE History Information in MR-DC | Huawei |
| R3-210393 | (TP for SON BLCR for 36.413 and 36.423) UE History Information in EN-DC | Huawei |
| R3-210497 | Discussion on collection of UE history information in EN-DC | NTT DOCOMO, INC. |
| R3-210560 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-210561 | (TP for SON BL CR for TS 37.340) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-210562 | (TP for SON BL CR for TS 36.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-210563 | (TP for SON BL CR for TS 38.413) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-210564 | (TP for SON BL CR for TS 38.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-210673 | (TP for SON BL CR for TS 36.413/38.413/36.423/38.423): UE History Information for Secondary Node | Ericsson |
| R3-210928 | UE history information in MR-DC | CMCC |
| R3-210929 | (TP to TS 36.413)UE history information in MR-DC | CMCC |
| R3-210930 | (TP to TS 36.423)UE history information in MR-DC | CMCC |
| R3-210931 | (TP to TS 38.413)UE history information in MR-DC | CMCC |
| R3-210932 | (TP to TS 38.423)UE history information in MR-DC | CMCC |
| R3-210991 | CB: # 1003_SONMDT_UEHist - Summary of email discussion | CATT - moderator |
| R3-211166 | CB: # 1003_SONMDT_UEHist - Summary of email discussion | CATT - moderator |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-210148 | Simple information on PRB utilisation per slice | Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, British Telecom, China Telecom |
| R3-210149 | (TP to TS 38.473, NR_ENDC_SON_MDT_enh-Core) Adding slice to the load information | Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, British Telecom, China Telecom |
| R3-210242 | Open issues on load balancing enhancement: SUL load | NEC |
| R3-210288 | (TP for SON BL CR 38.423) Adding slice to the load information | ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, British Telecom, China Telecom |
| R3-210306 | (TP on SON for 36.423) Discussion on PSCell MLB and SUL PRB usage | CATT |
| R3-210307 | (TP on SON for 38.423) Support of SUL PRB usage | CATT |
| R3-210308 | (TP on SON for 38.473) Support of SUL PRB usage | CATT |
| R3-210318 | Further discussion on the TNL load information | Nokia, Nokia Shanghai Bell |
| R3-210319 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| R3-210320 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| R3-210321 | Load information enhancements for BWP | Nokia, Nokia Shanghai Bell |
| R3-210394 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei |
| R3-210674 | (TP for SON BL CR for TS 38.423): MLB enhancements | Ericsson |
| R3-210675 | (TP for SON BL CR for TS 36.423): MLB enhancements | Ericsson |
| R3-210780 | Issue on load balancing enhancement | LG Electronics |
| R3-210894 | Slice PRB related load metric | CMCC |
| R3-210895 | TP to SON BLCR 38.423 on slice PRB | CMCC |
| R3-210896 | TP to SON BLCR 38.473 on slice PRB | CMCC |
| R3-210992 | CB: # 1004_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-211167 | CB: # 1004_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-211213 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| R3-211214 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-210076 | Definitions for MRO scenarios for SN change failure | Nokia, Nokia Shanghai Bell |
| R3-210077 | Definitions of SCG failure events for MRO for SN change | Nokia, Nokia Shanghai Bell |
| R3-210110 | Discussion on MRO for SN Change Failure | China Telecommunication |
| R3-210261 | TP for SON BLCR for 38.423: Support of SN change failure | Samsung |
| R3-210262 | TP for SON BLCR for 37.340: Support of SN change failure | Samsung |
| R3-210263 | LS on information needed for MRO in SCG Failure Report | Samsung |
| R3-210294 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-210295 | (TP on SN Change failure for 38.423) Addition of SCG Failure Information transfer | CATT |
| R3-210296 | [Draft]LS to RAN2 on SN change failure | CATT |
| R3-210395 | (TP for SON BLCR for 38.423) MRO for SN Change Failure | Huawei |
| R3-210396 | MRO for SN Change Failure | Huawei |
| R3-210397 | (TP for SON BLCR for 38.300) MRO for SN Change Failure | Huawei |
| R3-210565 | Further consideration on MRO SN change failure | ZTE |
| R3-210676 | On the SCG Failure Information delivery for MRO use case | Ericsson |
| R3-210677 | (TP for SON BL CR for TS 37.340): Definition of SCG change failure types | Ericsson |
| R3-210993 | CB: # 1005_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| R3-211168 | CB: # 1005_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| R3-211187 | MRO for PScell Change Failure | Samsung |
| R3-211189 | MRO for PScell Change Failure | Samsung, |
| R3-211209 | LS on information needed for MRO in SCG Failure Report | Samsung |
| R3-211332 | LS on information needed for MRO in SCG Failure Report | Samsung |
| R3-211333 | MRO for PScell Change Failure | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-210309 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-210310 | (TP on SON for 38.473) TP on PRACH coordination for F1AP | CATT |
| R3-210311 | (TP on SON for 36.423) TP on PRACH coordination for X2AP | CATT |
| R3-210442 | (TP for SON BL CR for TS 38.473): Left overs on RACH Optimization Enhancements | Huawei |
| R3-210443 | (TP for SON BL CR for TS 38.401):Stage 2 update for RACH Optimization | Huawei |
| R3-210566 | Left issue for Rel-16 RACH Optimization | ZTE |
| R3-210665 | RACH Optimization Further Discussion | Nokia, Nokia Shanghai Bell |
| R3-210666 | (TP for SON BL CR to TS 38.423) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-210667 | (TP for SON BL CR to TS 38.473) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-210678 | (TP for SON BL CR for TS 38.423): On delivering SN related RACH reports to the SN | Ericsson |
| R3-210679 | (TP for SON BL CR for TS 38.473): RACH conflict resolution and RACH report availability indication over F1 interface | Ericsson |
| R3-210994 | CB: # 1006_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-211170 | CB: # 1006_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-211207 | (TP for SON BL CR for TS 38.401):Stage 2 update for RACH Optimization | Huawei |
| R3-211255 | (TP on SON for 38.473) TP on PRACH coordination for F1AP | CATT |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-210246 | Coverage and Capacity Modification over F1 and Xn | NEC |
| R3-210260 | TP for SON BLCR for 38.300: Support of CCO | Samsung |
| R3-210345 | Coverage and Capacity Optimization | Qualcomm Incorporated |
| R3-210398 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | Huawei |
| R3-210399 | (TP for SON BLCR for 38.401 and 38.470) Coverage and Capacity Optimization | Huawei |
| R3-210662 | Considerations on beam aspects and split architecture for CCO | Nokia, Nokia Shanghai Bell |
| R3-210680 | (TP for SON BL CR for TS 38.300): CCO | Ericsson |
| R3-210681 | (TP for SON BL CR for TS 38.423): CCO | Ericsson |
| R3-210682 | (TP for SON BL CR for TS 38.473): CCO | Ericsson |
| R3-210798 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE, China Telecom, China Unicom |
| R3-210799 | (TP for SON BL CR 38.300) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-210800 | (TP for SON BL CR 38.423) Coverage and Capacity Optimization | ZTE, China Telecom, ZTE Unicom |
| R3-210801 | (TP for SON BL CR 38.473) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-210995 | CB: # 1007_SONMDT_CCO - Summary of email discussion | Huawei - moderator |
| R3-211078 | (TP for SON BL CR for TS 38.300): CCO | Ericsson |
| 10.2.3 | Inter-System Inter-RAT Energy Saving | |
| R3-210567 | Consideration on inter-system inter-RAT energy saving | ZTE |
| R3-210568 | (TP for SON BL CR for TS 36.300) RAN energy efficiency | ZTE |
| R3-210569 | (TP for SON BL CR for TS 38.300) RAN energy efficiency | ZTE |
| R3-210570 | (TP for SON BL CR for TS 38.413) RAN energy efficiency | ZTE |
| R3-210839 | Further Discussion on new Cell Status for Energy Saving Operation | China Telecom |
| R3-210909 | Discussion on inter-system inter-RAT energy saving | CMCC |
| R3-210910 | TP to 38.413 for inter-system inter-RAT energy saving | CMCC |
| R3-210996 | CB: # 1008_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| R3-211173 | CB: # 1008_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| 10.2.4 | Inter-System Load Balancing | |
| R3-210078 | Additional method for the inter-RAT load information exchange | Nokia, Nokia Shanghai Bell |
| R3-210400 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| R3-210683 | (TP for SON for TS 38.413, TS 38.300, TS 36.300): Inter-System Load Balancing BL CR | Ericsson |
| R3-210802 | Further Discussion on Inter-system Load Balancing in NR | ZTE, China Telecom, China Unicom |
| R3-210803 | (TP for SON BL CR 38.300) Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-210804 | (TP for SON BL CR 38.413) Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-210897 | More thoughts on inter-system load balancing | CMCC |
| R3-210898 | TP to 36.300 for inter-system load balancing | CMCC |
| R3-210899 | TP to 38.300 for inter-system load balancing | CMCC |
| R3-210997 | CB: # 1009_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| R3-211174 | CB: # 1009_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| 10.2.5 | Two-Step RACH Optimization | |
| R3-210664 | Scrambling Sequence Generation Coordination Between gNB | Nokia, Nokia Shanghai Bell |
| R3-210684 | (TP for SON BL CR for TS 38.423): 2-step RACH optimization for SON | Ericsson |
| R3-210998 | CB: # 1010_SONMDT_2StepRACH - Summary of email discussion | Ericsson - moderator |
| R3-211175 | CB: # 1010_SONMDT_2StepRACH - Summary of email discussion | Ericsson - moderator |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-210215 | Discussion on MRO for DAPS | Samsung |
| R3-210257 | Discussion on SON enhancements for CHO | Samsung |
| R3-210258 | TP for TS38.300: SON enhancements for CHO | Samsung |
| R3-210259 | TP for SON BLCR for 38.423: Support of CHO for MRO | Samsung |
| R3-210291 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-210292 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-210293 | [Draft]LS on Mobility Enhancement Optimization | CATT |
| R3-210401 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-210402 | [draft] LS on Mobility Enhancement Optimization | Huawei |
| R3-210552 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-210553 | (TP for SON BLCR for 38.300): MRO for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-210554 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility, ZTE |
| R3-210555 | (TP for SON BLCR for 38.300): MRO for DAPS handover | Lenovo, Motorola Mobility, ZTE |
| R3-210685 | (TP for SON BL CR for TS 38.300): DAPS handover SON aspects | Ericsson |
| R3-210686 | (TP for SON BL CR for TS 38.300): Conditional handover SON aspects | Ericsson |
| R3-210933 | SON Enhancement for CHO | CMCC |
| R3-210934 | SON Enhancement for DAPS | CMCC |
| R3-210999 | CB: # 1011_SONMDT_MobEnh - Summary of email discussion | Lenovo - Moderator |
| R3-211176 | CB: # 1011_SONMDT_MobEnh - Summary of email discussion | Lenovo - Moderator |
| R3-211196 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-211227 | Way forward on Scenarios for SON enhancements for CHO and DAPS HO | Lenovo, Motorola Mobility |
| R3-211303 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| 10.3.2.1 | MDT Enhancements | |
| R3-210444 | (TP for SON BLCR for TS 38.401): MDT coexistence with IDC | Huawei |
| R3-210445 | (TP for MDT BL CR for TS 38.473): MDT coexistence with IDC | Huawei |
| R3-210446 | (TP for MDT BL CR for TS 38.463): MDT coexistence with IDC | Huawei |
| R3-210447 | PLMN checking for MDT configuration during UE context retrieval | Huawei |
| R3-210556 | MDT Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-210557 | (TP for SON BL CR for TS 38.463 38.473 38.401) Introduce Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-210558 | Support Position method Enhancement Cell ID for MDT | ZTE |
| R3-210559 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| R3-210663 | (TP for MDT BL CR to TS 38.401) Impact of IDC on MDT | Nokia, Nokia Shanghai Bell |
| R3-210687 | (TP for MDT BL CR for TS 38.401): In-device coexistence “pollution” on MDT measurements Discussion | Ericsson |
| R3-210688 | (TP for MDT BL CR for TS 38.463): In-device coexistence “pollution” on MDT measurements | Ericsson |
| R3-210689 | (TP for MDT BL CR for TS 38.473): In-device coexistence “pollution” on MDT measurements | Ericsson |
| R3-210690 | LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Ericsson |
| R3-210749 | Impact of IDC on immediate MDT | Nokia, Nokia Shanghai Bell |
| R3-210750 | (TP for MDT BL CR to TS 38.463) Introduction of IDC indication for MDT | Nokia, Nokia Shanghai Bell |
| R3-211000 | CB: # 1012_SONMDT_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-211177 | CB: # 1012_SONMDT_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-211216 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| R3-211217 | (TP for MDT BL CR for TS 38.463): MDT coexistence with IDC | ZTE |
| R3-211261 | (TP for MDT BL CR for TS 38.463): MDT coexistence with IDC | Huawei |
| R3-211301 | (TP for MDT BL CR for TS 38.401): In-device coexistence “pollution” on MDT measurements Discussion | Ericsson |
| R3-211302 | LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Ericsson |
| R3-211316 | Limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT | ZTE |
| R3-211334 | LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Ericsson |
| R3-211335 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| R3-211336 | (TP for MDT BL CR for TS 38.463): MDT coexistence with IDC | Huawei |
| R3-211337 | (TP for MDT BL CR for TS 38.473): MDT coexistence with IDC | ZTE |
| 10.5 | SON/MDT Optimizations for NR-U | |
| R3-210733 | Proposals on MLB for NR-U | Ericsson |
| 13.1 | General | |
| R3-210346 | Updated Workplan for Rel-17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| 13.2.1.1 | Procedure Details | |
| R3-210100 | Inter IAB donor-CU topology adaptation | CATT |
| R3-210207 | Further considerations on inter-donor IAB Node Migration procedure | ZTE |
| R3-210216 | Discussion on inter-donor migration procedure for Rel-17 IAB | Samsung |
| R3-210347 | TP for BL CR to 38.401 on Inter-donor Topology Adaptation Procedures | Qualcomm Incorporated |
| R3-210389 | Inter-Donor IAB Node Migration Discussion | Intel Deutschland GmbH |
| R3-210429 | Considerations on top-down sequence during Inter-donor IAB node migration | KDDI Corporation |
| R3-210458 | Discussion on inter-donor IAB migration | Fujitsu |
| R3-210487 | discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-210541 | Discussion on inter-donor migration considering migration sequences | Google Inc. |
| R3-210547 | Inter-CU migration procedure | Huawei |
| R3-210721 | IAB Inter-donor Topology Adaptation | Ericsson |
| R3-211001 | CB: # 34_IAB_MigrationProcedureDetails - Summary of email discussion | Qualcomm - moderator |
| R3-211044 | IAB Inter-donor Topology Adaptation | Ericsson |
| R3-211199 | CB: # 34_IAB_MigrationProcedureDetails - Summary of email discussion | Qualcomm - moderator |
| R3-211200 | st2 TP capturing agreements | Qualcomm |
| R3-211239 | LS on DAPS-like solution for IAB | Qualcomm |
| R3-211240 | Inter-donor topology adaptation | Qualcomm |
| R3-211326 | LS on DAPS-like solution for IAB | Qualcomm |
| 13.2.1.2 | CHO and DAPS | |
| R3-210101 | CHO and DAPS for IAB | CATT |
| R3-210722 | Simultaneous Connectivity to Two IAB-donors and the Use of CHO | Ericsson |
| R3-211002 | CB: # 35_IAB_CHO-DAPS - Summary of email discussion | CATT - moderator |
| R3-211252 | CB: # 35_IAB_CHO-DAPS - Summary of email discussion | CATT - moderator |
| 13.2.2 | Reduction of Service Interruption | |
| R3-210102 | Reducing the Service Interruption for IAB | CATT |
| R3-210217 | Discussion on service interruption reduction for Rel-17 IAB | Samsung |
| R3-210348 | Interruption time reduction for Intra-donor IAB-node Migration | Qualcomm Incorporated |
| R3-210390 | Mitigation of Unnecessary Transmission | Intel Deutschland GmbH |
| R3-210459 | Discussion on reduction of service interruption | Fujitsu |
| R3-210488 | Discussion on Reduction of Service Interruption during Intra-Donor Topology Adaptation | Nokia, Nokia Shanghai Bell |
| R3-210548 | Inter-CU RLF recovery procedure | Huawei |
| R3-210657 | Service interruption reduction for intra-donor migration of IAB-node with descendant nodes | AT&T |
| R3-210716 | Discussion on reduction of service interruption in intra-donor migration and RLF recovery scenario | ZTE |
| R3-210723 | Reduction of Service Interruption in IAB Networks | Ericsson |
| R3-211003 | CB: # 36_IAB_Reduction_of_SrvInt - Summary of email discussion | Nokia - moderator |
| R3-211222 | CB: # 36_IAB_Reduction_of_SrvInt - Summary of email discussion | Nokia - moderator |
| R3-211223 | [draft] LS on using MOBIKE in Integrated Access and Backhaul system | Nokia |
| R3-211265 | CB: # 36_IAB_Reduction_of_SrvInt - Summary of email discussion | Nokia - moderator |
| R3-211266 | [draft] LS on using MOBIKE in Integrated Access and Backhaul system | Nokia |
| R3-211297 | LS on using MOBIKE in Integrated Access and Backhaul system | Nokia |
| 13.2.3 | Topology Redundancy | |
| R3-210218 | Discussion on CP-UP separation and inter-donor topology redundancy | Samsung |
| R3-210219 | CR on CP-UP separation over Xn for Rel-17 IAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics, Ericsson |
| R3-210349 | Backhaul transport for inter-donor redundancy | Qualcomm Incorporated |
| R3-210489 | discussion on Inter-CU topology redundancy | Nokia, Nokia Shanghai Bell |
| R3-210536 | Considerations on topological redundancy for IAB | LG Electronics |
| R3-210549 | Discussion on inter-donor topology management | Huawei |
| R3-210615 | Discussion on IAB inter-donor topology redundancy | Lenovo, Motorola Mobility |
| R3-210717 | Discussion on topology redundancy | ZTE |
| R3-211004 | CB: # 37_IAB_TopoRed - Summary of email discussion | Samsung - moderator |
| R3-211185 | CR on CP-UP separation over Xn for Rel-17 IAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics, Ericsson |
| R3-211186 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung |
| R3-211202 | CB: # 37_IAB_TopoRed - Summary of email discussion | Samsung - moderator |
| R3-211242 | CR on CP-UP separation over Xn for Rel-17 IAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics, Ericsson |
| R3-211243 | LS on inter-donor topology redundancy | Samsung |
| R3-211327 | CR on CP-UP separation over Xn for Rel-17 IAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-211329 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung |
| R3-211331 | LS on inter-donor topology redundancy | Samsung |
| 13.3.1 | Congestion Mitigation | |
| R3-210220 | Discussion on CP-based and UP-based congestion mitigation in Rel-17 IAB | Samsung |
| R3-210350 | Enhancements to congestion control for IAB | Qualcomm Incorporated |
| R3-210388 | Congestion Indication to CU-CP | Intel Deutschland GmbH |
| R3-210460 | Discussion on CP-based approach for DL and UL congestion mitigation in IAB networks | Fujitsu |
| R3-210490 | Analysis on Congestion mitigation | Nokia, Nokia Shanghai Bell |
| R3-210550 | Discussion on IAB E2E flow control | Huawei |
| R3-210614 | Discussion on congestion mitigation for IAB | Lenovo, Motorola Mobility |
| R3-210718 | Discussion on DL E2E flow and congestion control in R17-IAB | ZTE |
| R3-210724 | Congestion Mitigation in IAB Networks | Ericsson |
| R3-210725 | CR TS 38.425 IAB End-to-End Flow Control Feedback | Ericsson |
| R3-210781 | Issues on CP-based approach for DL congestion mitigation | LG Electronics |
| R3-211005 | CB: # 38_IAB_CongestionMitigation - Summary of email discussion | Ericsson - moderator |
| R3-211043 | CR TS 38.425 IAB End-to-End Flow Control Feedback | Ericsson |
| R3-211272 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-211330 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-211360 | CP-based Congestion Indication for IAB Networks | Ericsson |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-210103 | Inter-donor-DU local re-routing in IAB | CATT |
| R3-210221 | Discussion on inter-donor-DU local re-routing in Rel-17 IAB | Samsung |
| R3-210351 | Inter-donor-DU local rerouting for IAB | Qualcomm Incorporated |
| R3-210491 | discussion on Inter-Donor-DU re-routing | Nokia, Nokia Shanghai Bell |
| R3-210551 | Inter-donor-DU re-routing for IAB | Huawei |
| R3-210616 | Discussion on IAB packet rerouting | Lenovo, Motorola Mobility |
| R3-210719 | Considerations on inter-donor-DU re-routing | ZTE |
| R3-211006 | CB: # 39_IAB_MultiHopPerf - Summary of email discussion | Huawei - moderator |
| R3-211205 | CB: # 39_IAB_MultiHopPerf - Summary of email discussion | Huawei - moderator |
| R3-211241 | LS to RAN2 on inter-donor-DU re-routing | Huawei |
| R3-211298 | LS on inter-donor-DU re-routing | Huawei |
| 13.4.1 | CLI Management | |
| R3-210726 | Discussion on IAB duplexing enhancements | ZTE |
| 14.1 | General | |
| R3-210796 | Work plan for Rel-17 Further Multi-RAT Dual-Connectivity enhancements | Huawei |
| R3-211008 | CB: # MRDC1-work_plan - Summary of email discussion | Huawei - moderator |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-210085 | Principles for activation and deactivation of SCG resources | Nokia, Nokia Shanghai Bell |
| R3-210086 | Enabling fast SCG activation/deactivation | Nokia, Nokia Shanghai Bell |
| R3-210087 | Enabling fast SCG activation/deactivation | Nokia, Nokia Shanghai Bell |
| R3-210136 | MN initiated SCG activation and deactivation | Huawei, InterDigital |
| R3-210137 | Activation and de-activation of SCG | Huawei, InterDigital |
| R3-210138 | Activation and de-activation of SCG | Huawei, InterDigital |
| R3-210180 | Further discussion on SCG deactivation and activation | ZTE |
| R3-210181 | CR 37.340 for support of SCG activation/deactivation | ZTE |
| R3-210182 | CR 38.423 for support of SCG activation/deactivation | ZTE |
| R3-210239 | SCG Activation / deactivation discussion | NEC |
| R3-210266 | Discussion on SCG activation and deactivation | Samsung |
| R3-210267 | CR on SCG (de-)activation over F1 | Samsung |
| R3-210268 | CR on SCG (de-)activation over E1 | Samsung |
| R3-210352 | Signaling support for SCG deactivation/activation | Qualcomm Incorporated |
| R3-210403 | Support of SCG activation/de-activation | Ericsson |
| R3-210404 | Support of SCG activation/de-activation over X2 | Ericsson |
| R3-210405 | Support of SCG activation/de-activation over Xn | Ericsson |
| R3-210537 | Open issues on Activation Deactivation for One SCG and SCells | LG Electronics |
| R3-210597 | Left issues on SCG activation and deactivation | Lenovo, Motorola Mobility |
| R3-210598 | SCG activation and deactivation impact on E1 interface | Lenovo, Motorola Mobility |
| R3-210599 | Support of SCG Activation and Deactivation | Lenovo, Motorola Mobility |
| R3-210765 | Discussion on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-210766 | CR for TS 38.423 on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-210767 | CR for TS 38.473 on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-211009 | CB: # MRDC2-SCG_activation_deactivation - Summary of email discussion | ZTE - moderator |
| R3-211132 | CB: # MRDC2-SCG_activation_deactivation - Summary of email discussion | ZTE - moderator |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-210045 | LS on Conditional PSCell Addition/Change agreements | RAN WG2 |
| R3-210082 | Discussion on further details of the inter-SN CPC | Nokia, Nokia Shanghai Bell |
| R3-210083 | Enabling inter-SN conditional PSCell change | Nokia, Nokia Shanghai Bell |
| R3-210084 | Enabling inter-SN conditional PSCell change | Nokia, Nokia Shanghai Bell |
| R3-210106 | Discussion on Conditional PScell Addition/Change procedures | China Telecommunication |
| R3-210107 | CR on 36.423 for introducing CPAC information in SgNB Addition procedure | China Telecommunication |
| R3-210108 | CR on 38.423 for introducing CPAC information in SN Addition procedure | China Telecommunication |
| R3-210183 | Discussion on CPA and CPC | ZTE |
| R3-210184 | CR 36.423 for support of CPA and CPC | ZTE |
| R3-210185 | CR 38.423 for support of CPA and CPC | ZTE |
| R3-210186 | [draft] Reply LS on Conditional PSCell Addition/Change | ZTE |
| R3-210240 | discussion on Conditional PSCell Addition and PSCell Change | NEC |
| R3-210353 | CPA and MN initiated Inter-SN CPC procedures: preparation, execution, and data forwarding | Qualcomm Incorporated |
| R3-210354 | SN initiated Inter-SN CPC procedure: preparation, execution, and data forwarding | Qualcomm Incorporated |
| R3-210502 | (TP to TS 38.401) Consideration on conditional PSCell change/addition | Huawei |
| R3-210503 | Support of conditional PSCell change/addition | Huawei |
| R3-210504 | Support of conditional PSCell change/addition | Huawei |
| R3-210535 | Open issues on conditional PScell Change/Addition | LG Electronics |
| R3-210542 | TP for modification and release to prepared CPAC | Google Inc. |
| R3-210600 | Left issues on CPAC | Lenovo, Motorola Mobility |
| R3-210601 | [DRAFT] Reply LS on Conditional PSCell Addition/Change agreements | Lenovo, Motorola Mobility |
| R3-210744 | Support of conditional PSCell change/addition | Ericsson |
| R3-210745 | Conditional SN Addition | Ericsson |
| R3-210746 | Conditional SN Addition | Ericsson |
| R3-210768 | Some Considerations on How to Support CPAC | CATT |
| R3-210769 | Introduction of support CPAC | CATT |
| R3-210857 | Discussion on handling multiple PSCell candidates for CPAC | Samsung |
| R3-210861 | Correction on the preparation of one PSCell in one CPAC procedure | Samsung |
| R3-210862 | Correction on the preparation of multiple PSCells in one CPAC procedure | Samsung |
| R3-210877 | Correction on the preparation of one PSCell in one CPAC procedure | Samsung |
| R3-210945 | Regarding inter MN-SN signaling design for CPAC | Intel Corporation |
| R3-211010 | CB: # MRDC3-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| R3-211040 | LS on Conditional PSCell Addition/Change agreements | RAN WG2 |
| R3-211133 | CB: # MRDC3-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| R3-211134 | Reply LS on Conditional PSCell Addition/Change agreements | Samsung |
| R3-211338 | Reply LS on Conditional PSCell Addition/Change agreements | Samsung |
| 15.1 | General | |
| R3-210845 | Draft TR 38.890 | China Unicom |
| R3-211011 | CB: # NRQoE1-TR_update - Summary of email discussion | China Unicom - moderator |
| R3-211220 | TP to 38.890 on TR update | China Unicom |
| R3-211233 | TR 38.890 v0.3.0 | China Unicom - moderator |
| R3-211234 | Conclusion of NR QoE Management and Optimizations for Diverse Services SI in RAN3 | China Unicom |
| R3-211339 | TP to 38.890 on TR update | China Unicom |
| 15.2 | Triggering, Configuring, Measurement Collection and Reporting | |
| R3-210041 | LS Reply on New service type of NR QoE | SA WG4 |
| R3-210042 | LS reply on QoE Measurement Collection | SA WG4 |
| R3-210355 | QoE report suspending in RAN overload and RRC_IDLE/INACTIVE | Qualcomm Incorporated |
| R3-210356 | LS reply on QoE Measurement Collection | Qualcomm Incorporated |
| R3-210357 | RAN visible QoE | Qualcomm Incorporated |
| R3-210507 | Open issues in NR QoE solutions | Samsung |
| R3-210508 | Discussion on per slice QoE measurement | Samsung |
| R3-210509 | Discussion on radio related measurements and information in NR QoE | Samsung |
| R3-210510 | Discussion on RAN visible QoE and RAN triggered QMC | Samsung |
| R3-210527 | pCR for TR 38.890: Handling of QoE Measurement and Reporting and Support for New Services | Ericsson |
| R3-210528 | pCR for TR 38.890: QoE Visibility at the RAN | Ericsson |
| R3-210529 | pCR for TR 38.890: Mobility Support for NR QoE Management | Ericsson |
| R3-210530 | pCR for TR 38.890: QoE Support for Network Slicing | Ericsson |
| R3-210658 | (TP for TR 38.890) QoE measurement collection continuity vs. reporting continuity | Nokia, Nokia Shanghai Bell |
| R3-210659 | (TP for TR 38.890) QoE measurement configuration for specific UEs | Nokia, Nokia Shanghai Bell |
| R3-210660 | (TP for TR 38.890) RAN awareness of QoE measurement reports | Nokia, Nokia Shanghai Bell |
| R3-210661 | (TP for TR 38.890) Slice scope in QoE measurement activation and reports | Nokia, Nokia Shanghai Bell |
| R3-210770 | Discussion on support for NR QoE Mobility | CATT |
| R3-210771 | TP for support for NR QoE Mobility | CATT |
| R3-210772 | Discussion on RAN visible QoE configuration and reporting | CATT |
| R3-210773 | TP for RAN visible QoE configuration and reporting | CATT |
| R3-210809 | Further consideration on NR QoE service and procedure | ZTE Corporation |
| R3-210820 | Further discussions on the remaining open issues of QoE configuration and reporting | Huawei |
| R3-210821 | Further discussions on the remaining open issues of QoE report visibility at RAN | Huawei |
| R3-210822 | TP for TR 38.890 | ZTE Corporation |
| R3-210842 | Further discussion on scenarios and mechanisms for per slice QoE measurement | China Unicom |
| R3-210846 | Consideration on slice QoE measurement | ZTE |
| R3-210847 | More consideration on QOE mobility support | ZTE |
| R3-210848 | Further consideration on NR QoE service and procedure | ZTE |
| R3-210849 | TP for TR 38890 | ZTE |
| R3-210863 | Further discussions on the remaining open issues of support QoE during mobility | Huawei |
| R3-210864 | Further discussions on the remaining open issues of support slice for QoE | Huawei |
| R3-210900 | Remaining issues on NR QoE management | CMCC |
| R3-210901 | TP to 38.890 for NR QoE management | CMCC |
| R3-211012 | CB: # NRQoE2-Mobility - Summary of email discussion | Nokia - moderator |
| R3-211013 | CB: # NRQoE3-RANConfig_Report - Summary of email discussion | Huawei - moderator |
| R3-211014 | CB: # NRQoE4-Slice - Summary of email discussion | ZTE - moderator |
| R3-211015 | CB: # NRQoE5-RAN_visible - Summary of email discussion | Ericsson - moderator |
| R3-211190 | TP for Per slice QoE measurement | ZTE |
| R3-211201 | pCR for TR 38.890: QoE Visibility at the RAN | Ericsson |
| R3-211208 | TP to 38.890 on definitions | Samsung |
| R3-211210 | Void | ETSI-MCC |
| R3-211221 | Further discussions on the remaining open issues of QoE configuration and reporting | Huawei |
| R3-211229 | (TP for TR 38.890) RAN3#111-e agreements on mobility | Nokia - moderator |
| R3-211235 | (TP for TR 38.890) RAN3#111-e agreements on mobility | Nokia - moderator |
| R3-211236 | Further discussions on the remaining open issues of QoE configuration and reporting | Huawei |
| R3-211237 | TP to 38.890 on definitions | Samsung |
| R3-211238 | TP for Per slice QoE measurement | ZTE |
| R3-211281 | (TP for TR 38.890) RAN3#111-e agreements on mobility | Nokia - moderator |
| R3-211306 | pCR for TR 38.890: QoE Visibility at the RAN | Ericsson |
| R3-211307 | CB: # NRQoE5-RAN_visible - Summary of email discussion | Ericsson - moderator |
| R3-211312 | TP for Per slice QoE measurement | ZTE |
| R3-211320 | TP to 38.890 on definitions | Samsung |
| R3-211328 | TP to 38.890 on definitions | Samsung |
| R3-211340 | Further discussions on the remaining open issues of QoE configuration and reporting | Huawei, Samsung |
| R3-211341 | TP for Per slice QoE measurement | ZTE, Samsung, China Unicom, Ericsson |
| R3-211342 | pCR for TR 38.890: QoE Visibility at the RAN | Ericsson, Samsung, Qualcomm, CMCC |
| R3-211356 | (TP for TR 38.890) RAN3#111-e agreements on mobility | Nokia - moderator, Ericsson |
| R3-211357 | TP to 38.890 on definitions | Samsung, Ericsson, Huawei |
| R3-211358 | Further discussions on the remaining open issues of QoE configuration and reporting | Huawei, Samsung, Ericsson |
| 15.3 | Others | |
| R3-210358 | Ranking and prioritization of QoE enhancement features | Qualcomm Incorporated |
| R3-211016 | CB: # NRQoE6-Features_ranking - Summary of email discussion | Qualcomm - moderator |
| R3-211304 | CB: # NRQoE6-Features_ranking - Summary of email discussion | Qualcomm - moderator |
| R3-211305 | TP to 38.890 for QoE feature ranking | Qualcomm Incorporated |
| R3-211343 | TP to 38.890 for QoE feature ranking | Qualcomm Incorporated, Ericsson, Huawei |
| 16.1 | General | |
| R3-210112 | Work Plan for ePRN WI | China Telecommunication |
| R3-210826 | Consideration on the enhanced NPN WI scope | ZTE Corporation |
| R3-210827 | Consideration on RAN impact for eNPN | ZTE Corporation |
| R3-211036 | CB: # 1100_PRN_GEN - Summary of email discussion | China Telecom - moderator |
| 16.2 | Support for Standalone NPN | |
| R3-210638 | UE onboarding | Ericsson |
| 16.2.1 | Cell Access Control | |
| R3-210104 | Discussion on cell access control for eNPN | CATT |
| R3-210113 | On RAN support of SNPN along with credentials owned by a separate entitys | China Telecommunication |
| R3-210114 | On RAN support of UE onboarding and remote provisioning | China Telecommunication |
| R3-210159 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell |
| R3-210160 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell |
| R3-210161 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell |
| R3-210359 | RAN3 impacts of NPN onboarding and credential provisioning | Qualcomm Incorporated |
| R3-210476 | Supporting cell access control for enhanced NPN | Huawei |
| R3-210477 | Supporting cell access control for enhanced NPN | Huawei |
| R3-210907 | Support SNPN along with credentials owned by an entity separate from the SNPN | CMCC |
| R3-210908 | UE onboarding and provisioning for NPN | CMCC |
| R3-211037 | CB: # 1101_PRN_Onboarding - Summary of email discussion | Nokia - moderator |
| R3-211178 | LS on Support for Enhanced Non Public Network | Nokia, Nokia Shanghai Bell |
| R3-211179 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell |
| 16.2.2 | Connected Mode Mobility Support | |
| R3-210105 | Discussion on connected mode mobility support for eNPN | CATT |
| R3-210478 | Supporting connected mode mobility for enhanced NPN | Huawei |
| R3-210637 | SNPN and Service Provider (SP) separation | Ericsson |
| R3-210829 | Consideration on mobility support for key issue1 | ZTE Corporation |
| R3-210881 | Discussion on connected mode mobility in eNPN | LG Electronics |
| R3-211038 | CB: # 1102_PRN_Mobility - Summary of email discussion | Ericsson - moderator |
| 17.1 | General | |
| R3-210696 | Potential Feedback to SA2 on key issue#7 | Nokia, Nokia Shanghai Bell |
| R3-210902 | TR 38.832 v0.4.0 | CMCC, ZTE |
| R3-210903 | Revised Work Plan for RAN Slicing | CMCC, ZTE |
| R3-211017 | CB: # RANSlicing1-Workplan_Conclusion - Summary of email discussion | CMCC - moderator |
| R3-211228 | TR 38.832 v0.5.0 | CMCC |
| R3-211270 | CB: # RANSlicing1-Workplan_Conclusion - Summary of email discussion | CMCC - moderator |
| 17.2 | Mechanisms to Support Service Continuity | |
| R3-210360 | (TP for TR38.832) Evaluation of slicing solutions | Qualcomm Incorporated |
| R3-210505 | Discussion on solutions grouping | Samsung |
| R3-210506 | Discussion on solution evaluation | Samsung |
| R3-210524 | TP for 38.823 – Evaluation of Slice re-mapping solutions | Ericsson |
| R3-210525 | TP for 38.823 – structure of slice re-mapping solutions chapter | Ericsson |
| R3-210526 | TP for 38.823 – Resolution of editor’s notes and clarification of CN solution. | Ericsson |
| R3-210538 | Continuation of slicing solutions | Huawei |
| R3-210539 | Evaluation of slicing solutions | Huawei |
| R3-210540 | Conclusions of slice service continuity | Huawei |
| R3-210693 | Evaluation of Solutions for Slice Resource Shortage (Scenario 1) | Nokia, Nokia Shanghai Bell |
| R3-210694 | Evaluation of Solutions for Slice not supported at target (Scenario 2) | Nokia, Nokia Shanghai Bell |
| R3-210695 | Evaluation of Slice Remapping Policy | Nokia, Nokia Shanghai Bell |
| R3-210774 | Discussion on slice remapping scenarios | CATT |
| R3-210775 | TP for slice remapping scenarios | CATT |
| R3-210850 | Left issue of solutions | ZTE |
| R3-210851 | Evaluation on solutions | ZTE |
| R3-210852 | TP for TR38832 | ZTE |
| R3-210878 | Discussion on ENs for Slice remapping | LG Electronics |
| R3-210879 | (TP for 38.832) Text proposal to address ENs for Slice remapping | LG Electronics |
| R3-210904 | Evaluation of solutions on service continuity for slicing | CMCC |
| R3-210905 | Conclusion for service continuity on RAN slicing | CMCC |
| R3-210906 | TP to 38.832 for solution evaluation and conclusion | CMCC |
| R3-211018 | CB: # RANSlicing2-Slice_TP_cleanup - Summary of email discussion | ZTE - moderator |
| R3-211019 | CB: # RANSlicing3-Slice_Solutions_and_Evaluation - Summary of email discussion | Nokia - moderator |
| R3-211180 | Solutions for scenarios 2,4 handling legacy Ues | Nokia, Nokia Shanghai Bell |
| R3-211195 | Evaluation of slicing solutions | Huawei |
| R3-211203 | (TP for TR38.832) Evaluation of scenarios 2 and 4 | Qualcomm |
| R3-211211 | TP for TR38.832 Cleanup | ZTE |
| R3-211212 | TP for TR38.832 for conclusion on Solutions for scenarios 1,3,5,6 | ZTE |
| R3-211230 | TP to 38.832 for solution evaluation and conclusion | CMCC |
| R3-211231 | Evaluation of slicing solutions | Huawei |
| R3-211232 | Solutions for scenarios 2,4 handling legacy Ues | Nokia, Nokia Shanghai Bell |
| R3-211318 | Solutions for scenarios 2,4 handling legacy Ues | Nokia, Nokia Shanghai Bell |
| 20.1 | General | |
| R3-210014 | Support Non-Terrestrial Networks | Huawei |
| R3-210020 | NTN architecture aspects | THALES, Rakuten Mobile, Eutelsat, Inmarsat, Hughes Network |
| R3-210152 | NTN uplink synchronisation | THALES, Rakuten Mobile |
| R3-210703 | (TP for BL CR TS 38.300) NTN Stage 2 completion: Alignement with RAN2 | Huawei |
| R3-210704 | (TP for BL CR TS 38.300) NTN Stage 2 completion: Last email discussion comments and Agreements integration | Huawei |
| R3-210969 | CB: # 24_NTN_general - Summary of email discussion | Huawei - moderator |
| R3-210987 | Response paper to R3-210704 and R3-210703 | Ericsson |
| R3-211149 | (TP for BL CR TS 38.300) NTN Stage 2 completion | Huawei |
| R3-211150 | Support Non-Terrestrial Networks | Huawei |
| R3-211151 | CB: # 24_NTN_general - Summary of email discussion | Huawei - moderator |
| R3-211285 | RAN3 Feeback to RAN2 on NTN Running/BL CR | Huawei, Ericsson |
| R3-211286 | Support Non-Terrestrial Networks | Huawei |
| R3-211308 | Support Non-Terrestrial Networks | Huawei |
| R3-211309 | Support Non-Terrestrial Networks | Huawei |
| R3-211344 | Support Non-Terrestrial Networks | Huawei, Qualcomm |
| R3-211352 | Support Non-Terrestrial Networks | Huawei, Qualcomm |
| 20.2.1 | Network Identifier Handling | |
| R3-210361 | (TP for BL CR for TS 38.300) Handling of cell identity signalling towards the CN | Qualcomm Incorporated |
| R3-210362 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales |
| R3-210363 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales |
| R3-210470 | Discussion geographical fixed CGI reporting | CATT |
| R3-210492 | Discussion on cell ID handling on NG interface and Xn interface | Nokia, Nokia Shanghai Bell |
| R3-210911 | Discussion on Network Identifier Handling | CMCC |
| R3-210970 | CB: # 25_NTN_nwID - Summary of email discussion | Qualcomm - moderator |
| R3-211152 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales |
| R3-211153 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales |
| R3-211278 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-211279 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| 20.2.2 | Registration Update and Paging Handling | |
| R3-210364 | Paging optimization in NTN | Qualcomm Incorporated |
| R3-210471 | (TP for BL CR for TS 38.300) Support of location based paging for NTN | CATT |
| R3-210493 | Discussion on Registration Update and Page Handling | Nokia, Nokia Shanghai Bell |
| R3-210805 | Further Discussion on Paging Enhancement for NTN | ZTE |
| R3-210971 | CB: # 26_NTN_RegUpdate_Paging - Summary of email discussion | Nokia - moderator |
| 20.2.3 | Cell Relation Handling | |
| R3-210473 | Discussion on cell neighbouring information | CATT |
| R3-210494 | Discussion on Cell relation handling | Nokia, Nokia Shanghai Bell |
| R3-210705 | Support for non-terrestrial networks | Huawei |
| R3-210807 | Further Discussion on Cell Relation for NTN | ZTE |
| R3-210972 | CB: # 27_NTN_CellRelations - Summary of email discussion | ZTE - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-210119 | Discussion on feeder link switch-over for NTN | China Telecommunication |
| R3-210151 | NTN switch overs | THALES |
| R3-210472 | (TP for BL CR for TS 38.300) Support of Feeder Link Switch | CATT |
| R3-210495 | Discussion on Feeder Link Switchover | Nokia, Nokia Shanghai Bell |
| R3-210511 | Discussion on enhancements for feeder link switch over | Samsung |
| R3-210519 | Further Discussion on Feeder Link Switching | Ericsson LM |
| R3-210520 | Support for Feeder Link Switchover for Transparent Architecture | Ericsson LM |
| R3-210521 | Further Stage 2 Details for Feeder Link Switchover | Ericsson LM |
| R3-210671 | Feeder Link Switch | InterDigital Communications |
| R3-210706 | Update on feeder link switch for NTN for stage3 | Huawei |
| R3-210751 | Satellite information transfer over Xn | Intel Corporation |
| R3-210752 | NTN support in Xn | Intel Corporation |
| R3-210808 | Further Discussion on LEO Feeder Link Switch-over | ZTE |
| R3-210912 | Discussion on feeder link switch for NTN | CMCC |
| R3-210973 | CB: # 28_NTN_FeederSwitch - Summary of email discussion | Ericsson - moderator |
| 20.2.5 | Aspects Related to Country-Specific Routing | |
| R3-210365 | Discussion of scenarios for country specific routing | Qualcomm Incorporated |
| R3-210366 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated |
| R3-210474 | Discussion on country-specific CN selection | CATT |
| R3-210496 | Discussion on Country Specific Routing | Nokia, Nokia Shanghai Bell |
| R3-210516 | NTN Location Reporting for Country-Specific Routing | Ericsson LM |
| R3-210707 | Scenario related to Country-Specific Routing | Huawei |
| R3-210974 | CB: # 29_NTN_CountrySpecificRouting - Summary of email discussion | Qualcomm - moderator |
| R3-211154 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-211155 | NTN Location Reporting for Country-Specific Routing | Ericsson LM |
| 20.2.6 | Others | |
| R3-210518 | Further Discussion on Xn Functions and NTN | Ericsson LM |
| R3-210975 | CB: # 30_NTN_XnFunctions - Summary of email discussion | Ericsson - moderator |
| 21.1 | General | |
| R3-210697 | Revised Rel-17 NR IIoT/URLLC Work Plan | Nokia (Rapporteur) |
| R3-211020 | CB: # NRIIOT1-work_plan - Summary of email discussion | Nokia - moderator |
| 21.2 | Support for Propagation Delay Compensation Enhancements | |
| R3-210093 | RAN3 impacts of propagation delay compensation enhancements | Nokia, Nokia Shanghai Bell |
| R3-210200 | Analysis of Propagation Delay Compensation enhancements | ZTE |
| R3-210201 | CR for TS38.413 on propagation delay compensation enhancements | ZTE |
| R3-210202 | CR for TS38.473 on propagation delay compensation enhancements | ZTE |
| R3-210479 | RAN3 impacts of the time synchronization enhancement | Huawei |
| R3-210480 | Network-aware of the synchronization requirement | Huawei |
| R3-210481 | [Draft] LS on network-aware of the synchronization requirement | Huawei |
| R3-210482 | Time synchronization during handover | Huawei |
| R3-210776 | Discussion on Propagation Delay Compensation | CATT |
| R3-210777 | Discussion on time synchronization for mobility | CATT |
| R3-210778 | Discussion on Data interruption during mobility | CATT |
| R3-210783 | Discussion on supporting the propagation delay compensation | Samsung |
| R3-210784 | Discussion on the time synchronization enhancement during the mobility | Samsung |
| R3-210873 | Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization | Ericsson |
| R3-210874 | Enhancements for support of time synchronization | Ericsson |
| R3-210875 | Enhancements for support of time synchronization | Ericsson |
| R3-211021 | CB: # NRIIOT2-PDC - Summary of email discussion | Nokia - moderator |
| R3-211135 | CB: # NRIIOT2-PDC - Summary of email discussion | Nokia - moderator |
| R3-211136 | LS on gNB-based propagation delay compensation | Nokia |
| 21.3 | Enhancements Based on New QoS Related Parameters | |
| R3-210028 | Reply LS on Use of Survival Time for Deterministic Applications in 5GS | RAN WG2 |
| R3-210094 | RAN3 impacts of Survival Time | Nokia, Nokia Shanghai Bell |
| R3-210203 | Analysis of New QoS Related parameters | ZTE |
| R3-210289 | NR-U enhancement based on QoS related parameters | Samsung |
| R3-210483 | Introduction of the survival Time | Huawei |
| R3-210779 | Discussion on new QoS related parameters | CATT |
| R3-210876 | Discussion on Further enhanced NR-IIoT: QoS parameters related | Ericsson |
| R3-210919 | Enhancements to support new QoS related parameters | CMCC |
| R3-211022 | CB: # NRIIOT3-New_QoS_Parameters - Summary of email discussion | Samsung - moderator |
| R3-211137 | CB: # NRIIOT3-New_QoS_Parameters - Summary of email discussion | Samsung - moderator |
| 22.1 | General | |
| R3-210003 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-210004 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-210005 | Introduction of NR MBS | Lenovo, Motorola Mobility |
| R3-210015 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-210016 | MBS BL CR for TS38.410 | ZTE |
| R3-210017 | Introduction of NR MBS | Huawei, CMCC |
| R3-210036 | Reply LS on RAN impact of FS_5MBS Study | RAN WG2 |
| R3-210039 | LS on 5MBS progress and issues to address | SA WG2 |
| R3-210153 | RAN3 feedback on MBS issues to address in SA2 TR conclusions | Nokia, Nokia Shanghai Bell |
| R3-210154 | Reply LS on 5MBS progress and issues to address | Nokia, Nokia Shanghai Bell |
| R3-210223 | Introduction of NR MBS | Samsung |
| R3-210270 | Updated NR MBS work plan | Huawei,CMCC |
| R3-210271 | Consideration of SA2 LS on 5MBS progress and issues to address | Huawei |
| R3-210272 | [DRAFT] Reply LS on 5MBS progress and issues to address | Huawei |
| R3-210367 | BL CR for NR MBS for 38.413 | Qualcomm Incorporated |
| R3-210381 | Discussion of MSB LS from SA2(S2-2009235) | Intel Deutschland GmbH |
| R3-210632 | Discussion on SA2 LS on 5MBS progress and issues to address | Ericsson |
| R3-210633 | [DRAFT] Reply LS on 5MBS progress and issues to address | Ericsson |
| R3-210787 | Introduction of NR MBS | LG Electronics |
| R3-210923 | Discussion on SA2 LS on on 5MBS progress and issues to address | CMCC |
| R3-210924 | [Draft]Reply LS to SA2 on 5MBS Progress and Issues to address | CMCC |
| R3-211025 | CB: # 68_RANimpact_of_5MBSstudy - Summary of email discussion | Huawei - moderator |
| R3-211034 | CB: # 69_MBS_BLs - Summary of email discussion | CMCC - moderator |
| R3-211077 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-211145 | [DRAFT] Reply LS on 5MBS progress and issues to address | Huawei |
| R3-211146 | CB: # 68_RANimpact_of_5MBSstudy - Summary of email discussion | Huawei - moderator |
| R3-211296 | Reply LS on 5MBS progress and issues to address | Huawei |
| R3-211351 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| 22.2.1 | General Architecture | |
| R3-210162 | (TP for 38.300) QoS Model and MBS Session AMBR Enforcement | Nokia, Nokia Shanghai Bell |
| R3-210163 | (TP for 38.300) MBS Session Deactivation | Nokia, Nokia Shanghai Bell |
| R3-210164 | MBS Session Activation | Nokia, Nokia Shanghai Bell |
| R3-210465 | Some Considerations on MBS Architecture | CATT |
| R3-210512 | Discussion on NR MBS architecture | CHENGDU TD TECH LTD. |
| R3-210610 | Discussion on MBS session activation and deactivation | ZTE |
| R3-211026 | CB: # 70_MBS_Architecture - Summary of email discussion | Nokia - moderator |
| R3-211141 | (TP for 38.300) QoS Model and MBS Session AMBR Enforcement | Nokia, Nokia Shanghai Bell |
| R3-211147 | (TP for 38.300) QoS Model and MBS Session AMBR Enforcement | Nokia, Nokia Shanghai Bell |
| 22.2.2 | Session Management over NG | |
| R3-210165 | (TP for 38.300) Stage 2 for MBS Session Management | Nokia, Nokia Shanghai Bell |
| R3-210166 | MBS Session Management: MBS Context and UE MBS Context setup (stage 3) | Nokia, Nokia Shanghai Bell |
| R3-210224 | TP for MBS BLCR for 38.413-Session management for broadcasting over NG | Samsung |
| R3-210234 | TP for 38.413 on session management for broadcast service | CATT,CBN |
| R3-210273 | (TP to TS 38.410 BL CR and TS 38.413 BL CR) Multicast Session Management over NG | Huawei |
| R3-210274 | (TP to MBS TS38.410 BL CR) Support of Shared NG-U Transport | Huawei |
| R3-210275 | (TP to MBS TS38.413 BL CR) Support of Shared NG-U Transport | Huawei, CMCC |
| R3-210368 | NR Multicast Session Management Procedure | Qualcomm Incorporated |
| R3-210383 | Session Management Discussion | Intel Deutschland GmbH |
| R3-210602 | Considerations on MBS session management and TP to 38.410 38.413 BL CR | ZTE |
| R3-210603 | TP to 38.414 BL CR on IP multicast | ZTE |
| R3-210639 | Session Management over NG | Ericsson |
| R3-210640 | [TP for BL CR TS 38.300] TP on Session Management for NR MBS | Ericsson |
| R3-210641 | [TP for BL CR TS 38.410] TP on Session Management for NR MBS | Ericsson |
| R3-210642 | [TP for BL CR TS 38.413] TP on Session Management for NR MBS | Ericsson |
| R3-210920 | MBS Session management over NG | CMCC |
| R3-210921 | (TP to TS 38.410 ) MBS session management over NG | CMCC |
| R3-210922 | (TP to TS 38.300 ) MBS session management over NG | CMCC, Huawei |
| R3-211027 | CB: # 71_MBS_NGsessionMgmt - Summary of email discussion | Ericsson - moderator |
| 22.2.3 | Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State | |
| R3-210276 | (TP to TS 38.401 BL CR) Decision on PTP and PTM | Huawei |
| R3-210312 | Discussion on dynamic change between PTM and PTP | CATT |
| R3-210513 | Dynamic switch between PTM and PTP for RRC_CONNECTED UE | CHENGDU TD TECH LTD. |
| R3-210533 | Dynamic Change Between PTP and PTM | BEIJING SAMSUNG TELECOM R&D |
| R3-210604 | Mode switching for NR MBS | ZTE |
| R3-210605 | TP to 38.300 BL CR on mode change between PTP and PTM | ZTE |
| R3-210618 | (TP for BL CR 38.401) Dynamic switch between PTP and PTM | Lenovo, Motorola Mobility |
| R3-210782 | Issues on dynamic change between PTP and PTM | LG Electronics |
| R3-210913 | Discussion on dynamic change between PTP and PTM | CMCC |
| R3-211028 | CB: # 72_MBS_PTP-PTM_DynChg - Summary of email discussion | Samsung - moderator |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-210167 | (TP for 38.401) MBS F1, E1 Bearer Management | Nokia, Nokia Shanghai Bell |
| R3-210225 | TP for MBS BL CR for 38.463-Bearer management for broadcasting over E1 | Samsung |
| R3-210226 | TP for MBS BL CR for 38.473-Bearer management for broadcasting over F1 | Samsung |
| R3-210277 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei |
| R3-210278 | (TP to TS 38.470 and 38.460 BL CRs) Bearer management over F1 and E1 interfaces | Huawei |
| R3-210461 | Further Consideration on MBS context management over F1 and E1 | CATT |
| R3-210463 | TP for 38.463 on MBS Context Management at E1 interface | CATT |
| R3-210606 | Considerations on MBS bearer management over F1 and E1 and TPs to 38.470 38.473 38.460 38.463 BL CR | ZTE |
| R3-210607 | TP to 38.401 38.474 MBS BL CR on supporting IP multicast over F1-U | ZTE |
| R3-210619 | Open Issues on MBS Bearer Management over F1/E1 | Lenovo, Motorola Mobility |
| R3-210622 | User Plane Protocol Aspects for NR MBS | Lenovo, Motorola Mobility |
| R3-210914 | Discussion on MBS Bearer Management | CMCC |
| R3-211029 | CB: # 73_MBS_BearerMgmt_F1_E1 - Summary of email discussion | CATT - moderator |
| 22.2.5 | Others | |
| R3-210462 | Further Consideration on MBS Transmission Area | CATT |
| R3-210621 | (TP for BL CR 38.401) MBS Transmission Area Control between gNB-CU and gNB-DU | Lenovo, Motorola Mobility |
| R3-211030 | CB: # 74_MBS_Txarea - Summary of email discussion | Lenovo - moderator |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-210168 | (TP for 38.300) MBS Stage 2 for Mobility Management | Nokia, Nokia Shanghai Bell |
| R3-210169 | MBS Mobility User Plane Setup (stage 3) | Nokia, Nokia Shanghai Bell |
| R3-210170 | MBS Mobility Control Plane (stage 3) | Nokia, Nokia Shanghai Bell |
| R3-210171 | Support of MBS Seamless Mobility | Nokia, Nokia Shanghai Bell |
| R3-210172 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-210227 | Data forwarding for mobility between MBS supporting nodes | Samsung |
| R3-210228 | Coordinated assignment of PDCP SN | Samsung |
| R3-210279 | (TP to TS 38.300 BL CR) Mobility between MBS supporting nodes | Huawei, CMCC |
| R3-210280 | (TP to TS 38.401 BL CR) Mobility Between MBS Supporting Nodes | Huawei |
| R3-210281 | (TP to TS38.300 BL CR) Consideration on DL PDCP SN synchronization | Huawei, CMCC |
| R3-210282 | Support of NR MBS data transmission | Huawei |
| R3-210283 | (TP to TS38.300 BL CR) Data forwarding between MBS supporting nodes | Huawei |
| R3-210313 | Discussion on multicast context establishment during Xn-based handover | CATT |
| R3-210314 | Possible solutions to minimise data loss | CATT |
| R3-210315 | TP on TS 38.300 on MBS service continuity | CATT |
| R3-210369 | Data forwarding in handover with NR multicast | Qualcomm Incorporated |
| R3-210514 | Mobility between MBS supporting nodes | CHENGDU TD TECH LTD. |
| R3-210517 | PDCP SN Synchronization | vivo |
| R3-210534 | Issues on Mobility between MBS Supporting Nodes | LG Electronics |
| R3-210608 | Considerations on inter-gNB mobility for MBS | ZTE |
| R3-210609 | Considerations on lossless handover for NR MBS | ZTE |
| R3-210620 | Enhancements to support loss-less handover for NR multicast | Lenovo, Motorola Mobility |
| R3-210643 | On Support of mobility between gNBs supporting MBS | Ericsson |
| R3-210644 | [TP for BL CR TS 38.300] HO between supporting gNBs | Ericsson |
| R3-210645 | [TP for BL CR 38.410 and 38.413] HO between MBS supporting gNBs | Ericsson |
| R3-210646 | [TP for BL CR TS 38.423] HO between supporting gNBs | Ericsson |
| R3-210647 | [TP for BL CR TS 38.401] HO between supporting gNBs | Ericsson |
| R3-210760 | LS on MBS service continuity | CATT |
| R3-210915 | Discussion on Mobility with Service Continuity | CMCC |
| R3-210916 | TP to 38.300 BLCR for mobility between MBS supporting nodes | CMCC |
| R3-211031 | CB: # 75_MBS_Mobility_Supporting - Summary of email discussion | Samsung - moderator |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-210173 | (TP for 38.300) Mobility from MBS supporting to non-MBS supporting nodes | Nokia, Nokia Shanghai Bell |
| R3-210284 | (TP to TS38.300 BL CR) Mobility between MBS supporting and non-supporting nodes | Huawei |
| R3-210316 | Service continuity from non-MBS gNB toward MBS gNB | CATT |
| R3-210317 | Service continuity from MBS gNB toward non-MBS gNB | CATT |
| R3-210515 | Mobility between an MBS supporting node and a NON-MBS supporting node | CHENGDU TD TECH LTD. |
| R3-210648 | On support of mobility between MBS supporting and non-MBS supporting gNBs | Ericsson |
| R3-211032 | CB: # 76_MBS_Mobility_Non-supporting - Summary of email discussion | Huawei - moderator |
| 22.4 | Others | |
| R3-210285 | (TP to TS 38.300 BL CR) Service reception continuity for broadcast service | Huawei |
| R3-210464 | MBS reception of Idle and In-active Ues | CATT |
| R3-210623 | Considerations on measurements for NR MBS in idle/inactive | Lenovo, Motorola Mobility |
| R3-211033 | CB: # 77_MBS_SvcCont_InactiveUEs - Summary of email discussion | CATT - moderator |
| 23.1 | General | |
| R3-210843 | Discussion on WI scope and time plan for Enhanced eNB Architecture Evolution WI | China Unicom |
| 23.2.1 | General Principles, Functions and Procedures | |
| R3-210755 | CP-UP separation for eNBs | Ericsson |
| R3-210756 | General principles for eNB CP-UP separation | Ericsson |
| R3-210865 | General aspects and principles of the interface between CP and UP for eNB and ng-eNB | Huawei |
| R3-210866 | Initial stage 2 discussions for the interface between CP and UP for eNB and ng-eNB | Huawei |
| R3-210976 | CB: # 31_eNBarchEvol_General - Summary of email discussion | Huawei - moderator |
| 23.2.2 | Signaling Transport | |
| R3-210757 | E1 Signaling Transport for eNB CP-UP separation | Ericsson |
| R3-210869 | Initial discussions on general principles for signalling transport of the interface between CP and UP for eNB and ng-Enb | Huawei |
| R3-210870 | Further discussions on signalling transport of the interface between CP and UP for eNB and ng-eNB | Huawei |
| R3-210977 | CB: # 32_eNBarchEvol_SignalingTransport - Summary of email discussion | Huawei - moderator |
| 23.2.3 | Application Protocol | |
| R3-210758 | E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-210759 | E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-210867 | Bearer context management function and procedures of the interface between CP and UP for eNB and ng-eNB | Huawei |
| R3-210868 | Interface management function and procedures of the interface between CP and UP for eNB and ng-eNB | Huawei |
| R3-210978 | CB: # 33_eNBarchEvol_AP - Summary of email discussion | Ericsson - moderator |
| 30 | Other WIs/SIs Impacting RAN3 | |
| R3-210073 | Use cases for AI study | ZTE Corporation |
| R3-210174 | Signaling Support for Paging Cause | vivo |
| R3-210175 | BLCR36413 for Multi-USIM devices support | vivo |
| R3-210176 | BLCR37473 for Multi-USIM devices support | vivo |
| R3-210177 | BLCR38413 for Multi-USIM devices support | vivo |
| R3-210178 | BLCR38423 for Multi-USIM devices support | vivo |
| R3-210179 | BLCR38473 for Multi-USIM devices support | vivo |
| R3-210191 | Work plan for the INACTIVE small data WI | Rapporteur (ZTE) |
| R3-210192 | Discussion on support of small data transmission in INACTIVE state | Rapporteur (ZTE) |
| R3-210222 | Discussion on small data transmission for Inactive | Samsung |
| R3-210475 | Initial discussion on SDT data transmission | CATT |
| R3-210617 | Open issues of framework for AI | Lenovo, Motorola Mobility |
| R3-210653 | Discussion of the on-going RAN2 SI impacts | Ericsson, Huawei |
| R3-210654 | Reply LS to RAN2 | Ericsson |
| R3-210729 | Support for Multi-USIM devices | Nokia, Nolkia Shanghai Bell |
| R3-210730 | Support for Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-210731 | Support for Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-210732 | Enhancement for redundant PDU session WID | Nokia, Nokia Shanghai Bell |
| R3-210785 | High-level framework and definition for AI RAN | ZTE Corporation |
| R3-210795 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R3-210917 | Further discussion on high-level AI framework | CMCC |
| R3-210918 | AI based Energy Saving | CMCC |
| R3-210935 | TR 37.817 v0.1.0 | CMCC |
| R3-210979 | CB: # 16_Basket_SDT - Summary of email discussion | ZTE - moderator |
| R3-210980 | CB: # 17_Basket_AI - Summary of email discussion | CMCC - moderator |
| R3-210981 | CB: # 18_Basket_USIM - Summary of email discussion | Vivo - moderator |
| R3-210982 | CB: # 19_Basket_Rel-17Pos - Summary of email discussion | Ericsson - moderator |
| R3-210983 | CB: # 20_Basket_NB-IoT_MTC - Summary of email discussion | Huawei - moderator |
| R3-210984 | CB: # 21_Basket_RedPDUsessEnh - Summary of email discussion | Nokia - moderator |
| R3-211121 | Reply LS on Latency of NR Positioning Protocols | Ericsson |
| R3-211275 | CB: # 17_Basket_AI - Summary of email discussion | CMCC - moderator |
| R3-211314 | TP for TR 37.817 | CMCC |
| 31.1.1 | Inclusive Language Review | |
| R3-210044 | LS on Use of Inclusive Language in 3GPP | TSG SA |
| R3-210072 | Inclusive language cleanup for TS25.484 | ZTE Corporation |
| R3-210241 | Reviewing Inclusive Language in 38.401, 36.401, 25.412, 25.435, 25.468 | NEC |
| R3-210415 | Inclusive Language Review | Nokia, Nokia Shanghai Bell |
| R3-210417 | Inclusive language review for TS 25.467 | Nokia, Nokia Shanghai Bell |
| R3-210651 | Inclusive language review of TS 25.423 | Ericsson |
| R3-210652 | Inclusive language review of TS 25.703 | Ericsson |
| R3-210708 | Inclusive language review | Huawei |
| R3-210709 | Inclusive language review | Huawei |
| R3-210985 | CB: # 22_InclusiveLanguage - Summary of email discussion | InterDigital - moderator |
| R3-211039 | Further Guidance on Inclusive Language Review of 3GPP Specifications | RAN3 Chairman |
| R3-211084 | Inclusive language cleanup for TS25.484 | ZTE Corporation |
| R3-211148 | Inclusive language review for TS 25.467 | Nokia, Nokia Shanghai Bell |
| 31.2.1 | Local NG-RAN Node Identifier | |
| R3-210195 | Discussion on I-RNTI partitioning | ZTE |
| R3-210196 | CR38423 for addition of I-RNTI structure indication | ZTE |
| R3-210422 | Local NG-RAN node identifier | Nokia, Nokia Shanghai Bell |
| R3-210423 | Local NG-RAN node identifier | Nokia, Nokia Shanghai Bell |
| R3-210448 | Discussion on NG-RAN node ID resolution from I-RNTI | Huawei |
| R3-210728 | XnAP addition of Local NG-RAN Node Identifier | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-210734 | Node Identifier for RRC Inactive | Ericsson, AT&T, Verizon Wireless |
| R3-210735 | Addition of Local NG-RAN Node Identifier. | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-210736 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-210986 | CB: # 23_Local_NG-RANnode_ID - Summary of email discussion | Ericsson - moderator |
| R3-211131 | CB: # 23_Local_NG-RANnode_ID - Summary of email discussion | Ericsson - moderator |
| R3-211295 | CB: # 23_Local_NG-RANnode_ID - Summary of email discussion | Ericsson - moderator |
| 31.2.3 | PRACH Coordination Between LTE and NR | |
| R3-210449 | Scenarios and Requirements for Interference Coordination between LTE and NR | China Telecom,CATT,ZTE |
| R3-210583 | Consideration on the PRACH Coordination between LTE and NR | ZTE,China Telecom |